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
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.
With only one tool, there is no ambiguity. The tool's description clearly defines its purpose and limitations, leaving no room for confusion with other tools.
The single tool name 'get_pending_medicare_behavioral_health_preview' follows a clear verb_noun pattern, is descriptive, and internally consistent.
One tool is slightly thin but acceptable for a narrowly scoped preview server. The tool serves a specific, well-defined purpose without overreaching.
The tool surface is severely incomplete for the stated domain of pending Medicare enrollment data. It only provides a preview, lacking any CRUD operations, search, filtering, or data export capabilities, which would be necessary for agents to fully interact with the data.
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 declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds critical behavioral specifics: it cannot start runs, open checkout, contact applicants, or purchase anything—details beyond the annotations. No contradictions.
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 two sentences, front-loading the core purpose and then adding constraints. Every sentence is informative with no waste. It's appropriately sized for a simple preview tool.
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 the tool has one optional parameter and no output schema, the description covers essential aspects: preview size, content, limitations, and actions it cannot perform. It could briefly explain the 'full-edition handoff' but is otherwise complete.
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 description coverage is 100%. The single parameter 'states' is described in the schema as filtering the preview. The tool description does not add new semantic meaning beyond what the schema provides, so baseline score of 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 specifies the verb 'Return' and the resource: a validated 10-row public preview of behavioral-health NPIs from CMS files. It includes distinguishing details like source dates, national counts, limitations, and buyer-funded handoff, making the purpose unambiguous even without sibling tools.
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?
The description explicitly states what the tool cannot do (start Apify runs, open checkout, contact applicants, or purchase anything), providing clear when-not-to-use guidance. However, it does not compare to alternatives since no siblings exist, but the context is sufficient for an agent to decide when to invoke this preview tool.
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!