Skip to main content
Glama

medicare_info

Access Medicare data to analyze providers, hospitals, drug spending, formulary coverage, and quality metrics for healthcare research and decision-making.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYesThe operation to perform: - 'search_providers': Medicare Physician & Other Practitioners data - 'search_prescribers': Part D prescriber data - 'search_hospitals': Hospital utilization data - 'search_spending': Drug/service spending data - 'search_formulary': Part D formulary coverage - 'get_hospital_star_rating': Hospital overall quality star ratings (1-5) - 'get_readmission_rates': Hospital 30-day readmission rates by condition - 'get_hospital_infections': Hospital-acquired infections (HAI) data - 'get_mortality_rates': Hospital 30-day mortality rates - 'search_hospitals_by_quality': Find hospitals by quality metrics - 'compare_hospitals': Compare quality metrics across hospitals - 'get_vbp_scores': Hospital Value-Based Purchasing performance scores - 'get_hcahps_scores': Patient experience (HCAHPS) survey scores - 'get_asp_pricing': Medicare Part B ASP pricing data - 'get_asp_trend': ASP pricing trends over time - 'compare_asp_pricing': Compare ASP across drugs - 'get_formulary_trend': Track formulary changes over time (prior auth, tiers, coverage)
dataset_typeNoFor search_providers: Type of dataset to search. Options: - 'geography_and_service': Use when you need to compare regions, analyze geographic patterns, study regional variations in healthcare delivery, understand geographic distribution of healthcare services, or calculate per-capita/per-beneficiary rates by region. - 'provider_and_service': Use when you need to analyze individual provider performance, track specific procedures by provider, calculate total procedures across providers, or study provider-level service patterns and outcomes. - 'provider': Use when you need to analyze provider demographics, study provider participation in Medicare, understand provider practice patterns, or examine provider-level beneficiary characteristics and risk scores.
yearNoFor search_providers: Year of the dataset to query (2013 to latest available year, defaults to latest year).
hcpcs_codeNoFor search_providers: HCPCS code to search for (e.g., '99213' for established patient office visit).
provider_typeNoFor search_providers: Type of provider to search for (e.g., 'Cardiology', 'Podiatry', 'Family Practice').
geo_levelNoFor search_providers: Geographic level for filtering (e.g., 'National', 'State', 'County', 'ZIP').
geo_codeNoFor search_providers: Geographic code to filter by (e.g., 'CA' for California, '06037' for Los Angeles County).
place_of_serviceNoFor search_providers: Place of service code to filter by (e.g., 'F' for facility, 'O' for office, 'H' for hospital).
sizeNoNumber of results to return (default: 10 for search_providers, 25 for search_formulary, max: 5000).
offsetNoStarting result number for pagination (default: 0).
sort_byNoFor search_providers: Field to sort results by (e.g., 'Tot_Srvcs', 'Tot_Benes', 'Tot_Mdcr_Pymt_Amt').
sort_orderNoFor search_providers: Sort order ('asc' or 'desc', default: 'desc').
drug_nameNoFor search_prescribers: Drug name to search for - brand or generic (e.g., 'semaglutide', 'Ozempic', 'metformin'). Searches both brand and generic names.
prescriber_typeNoFor search_prescribers: Prescriber specialty (e.g., 'Endocrinology', 'Family Practice', 'Internal Medicine').
prescriber_npiNoFor search_prescribers: National Provider Identifier (NPI) of the prescriber.
stateNoFor search_prescribers, search_hospitals: State abbreviation (e.g., 'CA', 'TX', 'NY').
hospital_nameNoFor search_hospitals: Hospital name (partial match supported).
hospital_idNoFor search_hospitals: CMS Certification Number (CCN) or provider ID.
drg_codeNoFor search_hospitals (inpatient): Diagnosis Related Group (DRG) code.
spending_drug_nameNoFor search_spending: Drug name for spending analysis (brand or generic).
spending_typeNoFor search_spending: Type of spending data - 'part_d' (prescription drugs), 'part_b' (administered drugs). Default: 'part_d'.
formulary_drug_nameNoFor search_formulary: Drug name to search for (partial match supported, e.g., 'metformin', 'insulin'). At least one of formulary_drug_name or ndc_code is required.
ndc_codeNoFor search_formulary: NDC (National Drug Code) for exact drug identification (e.g., '00002143380'). At least one of drug_name or ndc_code is required.
tierNoFor search_formulary: Tier number to filter by (1=Preferred Generic, 2=Generic, 3=Preferred Brand, 4=Non-Preferred Brand, 5=Specialty, 6=Select Care).
requires_prior_authNoFor search_formulary: Filter by prior authorization requirement (true=requires PA, false=no PA required).
has_quantity_limitNoFor search_formulary: Filter by quantity limit (true=has limit, false=no limit).
has_step_therapyNoFor search_formulary: Filter by step therapy requirement (true=requires ST, false=no ST required).
plan_stateNoFor search_formulary: State abbreviation to filter plans (e.g., 'CA', 'TX', 'NY').
plan_idNoFor search_formulary: Medicare Part D plan ID to filter by specific plan.
quality_hospital_idNoFor hospital quality methods: CMS Certification Number (CCN) to lookup specific hospital (e.g., '050146').
quality_stateNoFor hospital quality methods: State abbreviation to filter hospitals (e.g., 'CA', 'TX', 'NY').
min_star_ratingNoFor search_hospitals_by_quality: Minimum star rating (1-5) to filter hospitals.
conditionNoFor get_readmission_rates/get_mortality_rates: Medical condition to filter by (e.g., 'heart_failure', 'pneumonia', 'heart_attack', 'copd', 'stroke').
infection_typeNoFor get_hospital_infections: Type of infection (e.g., 'CLABSI', 'CAUTI', 'SSI', 'CDIFF', 'MRSA').
metricsNoFor compare_hospitals: Array of metrics to compare (e.g., ['star_rating', 'readmission_rate', 'mortality_rate', 'infection_rate']).
hospital_idsNoFor compare_hospitals: Array of hospital CCN IDs to compare.
hcpcs_code_aspNoFor ASP pricing methods: HCPCS code for Part B drug (e.g., 'J9035' for Bevacizumab).
quarterNoFor get_asp_pricing: Quarter for ASP data (e.g., '2025Q1', '2024Q4').
start_quarterNoFor get_asp_trend: Starting quarter for trend analysis (e.g., '2023Q1').
end_quarterNoFor get_asp_trend: Ending quarter for trend analysis (e.g., '2025Q1').
hcpcs_codesNoFor compare_asp_pricing: Array of HCPCS codes to compare pricing.
hcahps_measureNoFor get_hcahps_scores: HCAHPS measure ID to filter by (e.g., 'H_COMP_1_A_P' for nurse communication, 'H_HSP_RATING_9_10' for hospital rating 9-10).
vbp_domainNoFor get_vbp_scores: VBP domain to filter by ('clinical_outcomes', 'person_community_engagement', 'safety', 'efficiency_cost_reduction', or 'all' for total performance score).
start_monthNoFor get_formulary_trend: Starting month in YYYYMM format (e.g., '202401' for January 2024).
end_monthNoFor get_formulary_trend: Ending month in YYYYMM format (e.g., '202512' for December 2025).
trend_metricNoFor get_formulary_trend: Metric to track ('prior_auth', 'tier', 'quantity_limit', 'coverage', or 'all'). Default: 'all'.
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions 'operations' but doesn't specify whether these are read-only queries, mutations, or mixed. It fails to disclose critical behavioral traits like rate limits, authentication needs, pagination behavior (implied by size/offset but not explained), error handling, or data freshness. For a complex tool with 46 parameters and no annotations, this is a significant gap.

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

Conciseness4/5

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

The description is appropriately concise with two sentences: one summarizing the tool's scope and another providing key usage guidance. It's front-loaded with the broad purpose, and every sentence adds value. However, it could be slightly more structured by explicitly categorizing the operations or mentioning the parameter count complexity.

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

Completeness2/5

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

Given the high complexity (46 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain return values, error conditions, or behavioral constraints. While the schema covers parameters well, the description fails to address the tool's overall behavior, making it inadequate for such a multifaceted tool without additional context.

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

Parameters3/5

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

The description adds minimal parameter semantics beyond the input schema, stating only that the 'method' parameter specifies the operation type. With 100% schema description coverage, the schema already documents all 46 parameters comprehensively. The description doesn't add syntax, format details, or contextual explanations beyond what's in the schema, meeting the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the tool's purpose as a 'unified tool for Medicare data operations' and lists the broad categories of operations (provider services, Part D prescribers, hospital data, etc.). It specifies that the 'method' parameter determines the exact operation, making the overall purpose clear. However, it doesn't distinguish from siblings (none exist) or provide specific verb+resource pairs for each operation type.

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

Usage Guidelines3/5

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

The description provides basic guidance by stating 'Use the method parameter to specify the operation type,' which implies that method selection determines when to use different functionalities. However, it lacks explicit when/when-not scenarios, prerequisites, or alternative tool recommendations. With no sibling tools, the guidance is adequate but minimal.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openpharma-org/medicare-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server