foundry-copilot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_NAME | Yes | The name of your Foundry agent. | |
| PROJECT_ENDPOINT | Yes | The endpoint of your Microsoft Foundry project. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_agent_toolA | Ask the Microsoft Foundry agent a question and return its answer. Use this for anything the agent is specialised in — its instructions, knowledge and tools all live server-side in Foundry, so you do not need to know how it works. Pass the user's request in plain language. Do NOT use this to read a Power BI model: |
| inspect_modelA | Connect to a Power BI semantic model and summarise what is in it. Accepts either a Fabric workspace and semantic model (by display name OR by the GUIDs from
the Fabric URL), or the path to a local PBIP / Read-only: it never modifies the model. Authentication is the user's own, so their
permissions and row-level security apply. Run this before |
| show_measureA | Show the current DAX expression of one measure, and the table it belongs to. Call |
| update_measure_daxA | Write a new DAX expression for a measure. MODIFIES THE MODEL. Read-only is the default everywhere else in this server; this is the one exception, and it is
opt-in twice over: the caller must pass The tabular engine validates the DAX, so an invalid expression is rejected rather than saved. |
| resolve_fabric_idsA | Turn the GUIDs in a Fabric URL into the display names the tools need. Use when the user pastes a Fabric Studio link instead of typing names. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear role: agent questions, model inspection, measure lookup, measure update, and ID resolution. The only potential ambiguity is ask_agent_tool could be used for model tasks, but its description explicitly directs direct inspection to inspect_model.
All tools follow a consistent verb_first snake_case pattern (ask_, inspect_, show_, update_, resolve_). Names clearly indicate action and target.
5 tools is ideal for a focused server—enough to cover core operations without bloat.
Covers inspect and update workflows for measures, but lacks create/delete measure operations. The agent can fill gaps, but as a direct tool surface it is slightly incomplete.