CMS Medicare Data
Server Details
Medicare spending, chronic conditions, hospital quality, readmissions, and enrollment
- 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 3.8/5 across 5 of 5 tools scored.
Each tool targets a distinct data domain within Medicare: chronic conditions, hospital quality, hospital readmissions, enrollment, and spending. The descriptions clearly differentiate their purposes with no overlap in functionality. An agent can easily select the right tool based on the specific data need.
All tools follow a consistent 'get_[domain]_[metric]' naming pattern using snake_case. This predictable structure makes it easy to understand what each tool retrieves. The naming convention is uniform across all five tools without any deviations.
Five tools is well-scoped for a Medicare data server, covering key areas like conditions, hospital metrics, enrollment, and spending. Each tool earns its place by addressing a distinct aspect of Medicare data analysis. The count is neither too sparse nor overwhelming for the domain.
The toolset provides comprehensive coverage of Medicare data domains with clear retrieval operations. Minor gaps exist, such as no tools for provider-level data or prescription drug spending details, but the core areas are well-covered for geographic and hospital-level analysis. Agents can perform most common Medicare data queries effectively.
Available Tools
5 toolsget_chronic_conditionsInspect
Get prevalence of chronic conditions among Medicare beneficiaries.
Returns state-level data on 21 chronic conditions including diabetes,
heart failure, COPD, depression, Alzheimer's, and more. Useful for
understanding disease burden by geography.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'TX').
condition: Chronic condition name to filter by (e.g. 'diabetes',
'heart failure', 'COPD', 'depression').
year: Year of data (e.g. 2022).
limit: Maximum number of records to return (default 50, max 1000).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| limit | No | ||
| state | No | ||
| condition | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_hospital_qualityInspect
Get hospital quality star ratings and general information.
Returns hospital quality data including overall star ratings,
location details, and hospital type. Filter by state or city.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'TX').
city: City name to filter by (e.g. 'Chicago', 'Houston').
limit: Maximum number of records to return (default 50, max 1000).
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| limit | No | ||
| state | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_hospital_readmissionsInspect
Get 30-day hospital readmission rates by hospital.
Returns hospital-level readmission data including excess readmission
ratios and predicted/expected readmission rates for conditions like
heart attack, heart failure, and pneumonia.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'TX').
hospital_name: Hospital name or partial name to search for.
limit: Maximum number of records to return (default 50, max 1000).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | No | ||
| hospital_name | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_medicare_enrollmentInspect
Get Medicare enrollment data by state and county.
Returns enrollment counts including total beneficiaries, Original
Medicare vs Medicare Advantage enrollment, and Part D enrollment.
Useful for understanding Medicare population by geography.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'TX').
year: Year of enrollment data (e.g. 2022).
limit: Maximum number of records to return (default 50, max 1000).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| limit | No | ||
| state | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_medicare_spendingInspect
Get Medicare spending per beneficiary by geographic area.
Returns geographic variation in Medicare spending including per-capita
costs and total spending amounts. Filter by state, county, or year.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'TX').
county: County name to filter by (e.g. 'Los Angeles').
year: Year of spending data (e.g. 2022).
limit: Maximum number of records to return (default 50, max 1000).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| limit | No | ||
| state | No | ||
| county | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
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!