Pending Medicare Enrollment Data
Server Details
Behavioral health NPIs newly pending Medicare provider enrollment; free validated preview.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- unitedideas/pending-medicare-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no ambiguity with other tools.
With a single tool, naming consistency is perfect by default.
One tool is minimal but may be appropriate for a preview-only scope; however, the domain suggests additional tools would be useful.
The tool only provides a preview; missing functionality for full data retrieval or purchase, which is hinted but not implemented.
Available Tools
1 toolget_pending_medicare_behavioral_health_previewGet pending Medicare behavioral-health data previewARead-onlyIdempotentInspect
Return the current validated 10-row public preview of behavioral-health NPIs newly present in CMS pending first-time Medicare enrollment files, with source dates, national counts, limitations, and an optional buyer-funded full-edition handoff. This read-only tool cannot start an Apify run, open checkout, contact applicants, or purchase anything.
| Name | Required | Description | Default |
|---|---|---|---|
| states | No | Optional two-letter state or territory codes used to filter the public 10-row preview. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint=false. The description goes further by explicitly listing actions the tool cannot perform (start Apify run, open checkout, contact applicants, purchase). This adds significant behavioral context beyond annotations, with no contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently conveys all necessary information, but it is long and could be structured as two sentences for better readability. It is front-loaded with the main purpose, earning a 4.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given only one optional parameter, no output schema, and no sibling tools, the description fully covers what the tool returns, filtering capability, limitations, and what it cannot do. No gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the 'states' parameter well-described in the schema itself. The description adds no additional meaning beyond mentioning filtering; thus baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a 10-row public preview of behavioral-health NPIs from CMS, including specific details like source dates, national counts, and limitations. The verb 'Return' and resource are unambiguous, and since there are no sibling tools, it effectively distinguishes its function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
While the description explains what the tool does, it does not explicitly state when to use it or provide alternatives. However, with no sibling tools, the usage context is clear. A slight score reduction for missing explicit 'when to use' guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!