Copilot agents not able to understand requests schema while calling MCP tools

(0) Share

Report

Posted on by sohilbhalla

Hello,

I have a remote MCP server running which has multiple tools running over HTTP Streamable. One of the tool has the request format as

public class WorkspaceContext
{
public long WorkspaceId { get; set; }
public string? Concern { get; set; }
public string? Company { get; set; }
}

When the copilot agent tries to connect to the mcp tool it passes the request as

{
"company": {
"code": "12"
},
"concern": {
"code": "11"
},
"workspaceId": 111245
}
which keeps on failing. Even after doing tools-list and getting the request schema, agents don't follow it.

These cases works when we have simple request types like string, int etc. but for the complex ones it fails.

I have the same question (4)

All responses (1)

Answers (0)

dezrrm 10 on at

Like (0)

Report

Copilot agents not able to understand requests schema while calling MCP tools

I think you need to dumb it down for it. Like you said, it works with simple request types. I've had similar issues with it not understanding optional parameters.

It won't ask the user if they want to fill something in for those parameters, so this is in the instructions for the non-optional parameter and it works:
"Ask the user the Name of the contact associated with the task (optional). Submit 'no contact' if user does not want a contact."

You didn't say what the schema should be so I'll just make something up:

public class WorkspaceContext
{
public long WorkspaceId { get; set; }
public string ConcernCode { get; set; }
public string CompanyCode { get; set; }
}

and then transform that into the shape you need for your internal API.

Was this reply helpful? Yes No