Skip to main content
Glama

Medicare Hospital Wage Index

medicare_hospital_wage_index
Read-onlyIdempotent

What is the Medicare IPPS hospital wage index for a metro area (CBSA) and fiscal year? Returns the wage index CMS applies to hospital inpatient payment in a CBSA, with the GAF, the reclassified wage index, the value before frontier / rural-floor / imputed-floor adjustment, and which floors applied. Answers "Medicare hospital wage index for Boston FY2025", "hospital wage index CBSA 14454 FY2025", "IPPS wage index for Los Angeles-Long Beach-Anaheim", "wage index New York-Jersey City-White Plains FY2026", "rural wage index for Alabama". Pass cbsa (5-digit metro code, or the 2-digit state code for a statewide rural area) and/or area (a metro name, "Boston" or "Boston, MA") and/or state; fiscal_year (FY2022-FY2027 loaded) defaults to the newest and is stated. A CBSA that spans states can carry a different wage index per state, so the per-state rows are always returned. An unmatched CBSA returns found:false, never a nearby area. This is the hospital inpatient wage index, not the physician GPCI (medicare_gpci_lookup) or the FQHC GAF (medicare_fqhc_gaf). Sourced from the CMS IPPS final-rule wage index tables.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "area": "Boston",
      "fiscal_year": 2025
    },
    "name": "medicare_hospital_wage_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoMetro area name or part of it ("Boston", "Los Angeles", "Boston, MA"). The part after a comma is read as the state.
cbsaNoCBSA code, e.g. "14454" (Boston) or "31084" (Los Angeles-Long Beach-Glendale; the retired code 31080 returns its successors 31084 and 11244); a 2-digit state code (e.g. "01") selects that state's rural area.
stateNoOptional state code or name; alone, lists every CBSA with a row in that state.
fiscal_yearNoFederal fiscal year, e.g. 2025. Omit for the newest loaded year (stated in the response).

Output Schema

NameRequiredDescriptionDefault
hintNo
areasNo
foundNo
notesNo
reasonNo
sourceNo
truncatedNo
area_countNo
data_as_ofNo
fiscal_yearNo
loaded_rangeNo
copy_captured_atNo
legacy_cbsa_noteNo
year_was_defaultedNo
loaded_fiscal_yearsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety bar is low; the description nonetheless adds real behavior: the fiscal-year default and its being echoed in the response, the always-returned per-state rows for multi-state CBSAs, the no-fuzzy-match failure mode, and the data source (CMS IPPS final-rule tables). What it doesn't cover, such as response size or how many rows a bare state query returns, is minor against a present output schema.

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?

Front-loads the core question and return contents before parameters and exclusions, and the example queries do real routing work. It is dense but slightly redundant with the 100%-covered schema, particularly in re-explaining what cbsa and area accept.

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

Completeness5/5

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

An output schema exists, so return-shape explanation is unnecessary, and the description still flags the two things an agent must know about returns: per-state rows and found:false for misses. Together with source attribution and the sibling exclusions, nothing needed to call this correctly is missing.

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?

Schema description coverage is 100%, so the baseline is 3 and the schema already explains the 2-digit state code convention for rural areas and the retired 31080 code behavior. The description mostly restates those details, adding only the loose 'and/or' combination semantics and the note that per-state rows accompany a spanning CBSA.

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?

Opens with a specific question form naming the exact resource (Medicare IPPS hospital wage index) and the two keying dimensions (CBSA and fiscal year), then enumerates the returned components (GAF, reclassified index, pre-adjustment value, floors applied). It explicitly excludes two named siblings, medicare_gpci_lookup and medicare_fqhc_gaf, so an agent can separate it from adjacent payment tools without reading a schema.

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

Usage Guidelines5/5

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

Gives concrete natural-language query patterns ("Boston FY2025", "CBSA 14454 FY2025", "rural wage index for Alabama") plus how the three selectors combine via AND/OR. It states the default behavior for fiscal_year, the loaded year range FY2022-FY2027, and the negative case that an unmatched CBSA returns found:false rather than a nearby area.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.