CMS Medicare Data

get_medicare_enrollment

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).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	No
`limit`	No
`state`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the burden. It discloses return contents, defaults, and max limit, which is helpful. However, it omits any mention of required vs optional parameters, error behavior, or what happens if 'state' is omitted, despite the schema showing no required params. It also mentions 'county' in the description but no county parameter exists, which is a minor inconsistency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise paragraphs followed by a tight Args list. It front-loads the purpose and return value, then gives precise parameter details. No fluff or redundant lines.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description doesn't need to detail return fields. The description covers purpose, return value, and parameter semantics. The only gap is the state/county mismatch and the lack of guidance on optional parameters, which is a minor omission given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, which it does thoroughly. The Args section explains the format for 'state' ('Two-letter US state abbreviation'), provides an example for 'year', and states the default and max for 'limit'. All three parameters are given meaningful context beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies an exact action ('Get Medicare enrollment data'), resource ('Medicare enrollment data'), and scope ('by state and county'). It clearly distinguishes from siblings like get_chronic_conditions or get_hospital_quality by focusing on enrollment counts and geographic granularity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Useful for understanding Medicare population by geography' provides clear context for when this tool is appropriate. It doesn't explicitly mention exclusions or alternatives, but given the sibling tool names are topically different, the intended use is obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CMS Medicare Data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct Medicare dataset: chronic conditions, hospital quality, hospital readmissions, enrollment, and spending. There is no overlap in purpose or output, making tool selection unambiguous.

Naming Consistency5/5

All tool names follow a consistent 'get_' prefix followed by a clear domain noun (e.g., get_chronic_conditions, get_hospital_quality). This predictable verb_noun pattern holds across all tools with no exceptions.

Tool Count5/5

With 5 tools, the server is well-scoped for a focused Medicare data access API. Each tool covers a major data category, and the number is neither too few to be useful nor too many to be unwieldy.

Completeness4/5

The tool set covers core Medicare data domains: conditions, hospital performance, readmissions, enrollment, and spending. Minor gaps exist (e.g., no provider directory or drug spending data), but the current set addresses primary use cases without significant dead ends.

Resources

Need Help?