MCP request successful but output not loaded into agent context

(2) Share

Report

Posted on by AW-23101259-0

I have successfully connected an MCP server as a tool to my Agent in Copilot studio. The agent is able to use the MCP server as a tool call, however the output of the MCP is not accessed by the agent. I am able to inspect the tool call in the activity map, where I can see both structured output and raw output. In all my testing the output is correct and is response that I am looking for but the information is simply not within the scope of the agent. The output is not being loaded into the agent's context. This bug renders my MCP server useless.

Things I have tried:

- Removing the tool and adding it back again.

- Creating a new agent.

- Instead of using my own custom MCP server, I used the Microsoft Learn Docs MCP (An MCP developed by Microsoft to engage with docs). I observe the exact same error, where the MCP is being used correctly and output (in the activity map) matches what I expect. The agent simply cannot interact with this output.

If anyone has had the same issue or knows of a workaround, please let me know.

Thanks!

Categories:

Model context protocol

I have the same question (4)

All responses (7)

Answers (0)

Romain The Low-Code... 2,562 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

hello,

did you check inside you'r swagger in the custom conenctor if you have output variable ?

Most of the time the problem for me came from a instruction in the global instruction of the agent wich block the answer, did you try to remove all instruction ?

Was this reply helpful? Yes No
SM-24101631-0 2 on at

Like (0)

Report
Copy link

Link copied!

I am facing the exact same issue, can someone please help

Was this reply helpful? Yes No
AW-23101259-0 6 on at

Like (0)

Report
Copy link

Link copied!

Hi Romain,

I checked inside the swagger file for my connector and could not see a clear output variable defined. I looked online and could not find an example of this. I was hoping you could maybe show me an example of how a swagger file can describe output variables.

Regarding your comment about the global instructions to the agent. I have tried removing all instructions for the agent and the problem still persists.

Thanks for the reply!

Andreas

Was this reply helpful? Yes No
ZZ-03112155-0 2 on at

Like (0)

Report
Copy link

Link copied!

Same issue here, the testing UI even shows the output as expected, with isError=false and output in the form of the below. Yet the model insists it can't see any of it most of the time. Maybe 2% of the time it IS able to see the content.

The MCP server works just fine with any other platform connected to it (Claude, ChatGPT, etc.), so this seems to be a Copilot / Power Automate connector issue.

[

{

"text": ... ,

"type": "text"

}

]

Was this reply helpful? Yes No
YB-08021419-0 5 on at

Like (0)

Report
Copy link

Link copied!

Similar issue here - as of 24.11.2025 a Copilot Agent with a Dataverse MCP tool stopped responding in Test window, not even with an error output. No actions are displayed in the Activity sub-window.
On 27.11.2025 I've created a new Agent, with the same settings (instructions, tools, knowledge etc.) - the Agent responds (in Test), but completely ignores the output of the Dataverse MCP tool.

Was this reply helpful? Yes No
Suggested answer

Romain The Low-Code... 2,562 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@AW-23101259-0 if you wan't some sample did you try the tutorial from https://github.com/microsoft/mcsmcp during a long time it was the official tutos :) and a great content with a lot of code sample.

Was this reply helpful? Yes No
Suggested answer

YB-08021419-0 5 on at

Like (0)

Report
Copy link

Link copied!

I've managed to fix the issue for myself.

I've noticed that a custom agent within a different environment did not have an issue using a Dataverse MCP Server.

So I've created a new small table in my current environment and a new "clean" agent there as well.

That Agent happened to have no issue quering that table via Dataverse MCP Server. I've instructed it to query an original table, which I've had problem with - no problem as well.

So in my case:
- it wasn't an issue with an Environment
- it wasn't an issue with a Dataverse Table
- it wasn't an issue with a Connection (I've deleted and created new Dataverse connection mutliple time)
- it wasn't an issue with a Dataverse MCP Server tool

It was some bug within my original custom agent - which disappeared as soon as I've created a new one.

The d*mn thing tortured me for 2 weeks.

But then ~~I got an arrow in my knee~~ , after having the Dataverse MCP Server tool working, it turned out the read_query tool is limited to 20 rows per query - which essentially made Dataverse MCP Server useless to me.

Was this reply helpful? Yes No