Fabric 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_toolC | Recommends the best Fabric pattern tool for a given task |
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
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.
The single tool name 'recommend_tool' follows a consistent verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.
A single tool is too few for most server purposes, as it severely limits functionality and scope. This feels thin and incomplete for a server named 'Fabric MCP Server', which might imply broader capabilities.
The server is severely incomplete; with only a recommendation tool, there are obvious gaps in the surface. It lacks any tools to actually execute or manage Fabric patterns, making it impossible for agents to perform core tasks beyond getting advice.