adf-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Report that the MCP server is up and configuration loaded correctly. Useful as a first call from any MCP client (VS Code, Claude Code) to confirm the server started, before any Azure-dependent tools exist. |
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 1 tool
There is only one tool, so no agent could confuse it with another. The health_check tool has a clear and unique purpose as a readiness probe.
The single tool name is clean and uses standard snake_case; however, with only one tool, no meaningful set-wide naming convention is established.
A server named adf-mcp-server exposing only a health_check tool is far below the minimum viable tool surface. This is a single trivial tool, which matches the lowest end of the scale.
The server gives agents no way to interact with the Azure Data Factory domain at all. A health check alone is severely incomplete and leaves every meaningful user workflow unavailable.