Medicare 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 |
|---|---|
| medicare_infoB | Unified tool for Medicare data operations: provider services, Part D prescribers, hospital data, spending information, hospital quality metrics, and ASP pricing. Use the method parameter to specify the operation type. |
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. The single tool clearly handles all Medicare data operations, so an agent cannot misselect between different tools.
The single tool name 'medicare_info' follows a clear and consistent pattern. Since there is only one tool, there is no inconsistency in naming conventions to evaluate.
A single tool for a broad domain like Medicare data operations is too few. The tool consolidates multiple distinct operations (provider services, Part D prescribers, hospital data, etc.) into one, which can lead to complexity and reduced clarity for agents.
The tool claims to cover a wide range of Medicare data operations, but as a single tool, it may lack granularity. While it mentions provider services, Part D, hospital data, spending, quality metrics, and ASP pricing, the actual completeness depends on the implementation of the 'method' parameter.