Skip to main content
Glama

CMS Medicare inpatient hospital averages per MS-DRG

health_medicare_inpatient_drg
Read-only

CMS Medicare inpatient hospital averages per MS-DRG (data.cms.gov, fee-for-service Part A): hospital name, state, DRG code and description, discharges, average submitted charge, average total payment and average Medicare payment. Hospital-level averages, not the IPPS national rate table. Filter by 3-digit DRG code and optional state; up to 20 rows. Related tools on this server, for a different need: health_medicare_advantage_star when you need official CMS Medicare Star Ratings for Medicare Advantage. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drg": "<drg>"
    },
    "name": "health_medicare_inpatient_drg"
  }
}

Input Schema

NameRequiredDescriptionDefault
drgYes3-digit MS-DRG code, e.g. 871
maxNoHow many rows, 1 to 20 (default 5)
stateNoTwo-letter state code, optional

Output Schema

NameRequiredDescriptionDefault
drgNo
stateNo
sourceNo
checkedAtNo
hospitalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the commercial and scoping context: $0.002 per successful call via x402 USDC on multiple networks, no charge for failures, hospital-level rather than national averages, and a hard 20-row cap. Those are real behaviors an agent cannot infer from annotations.

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?

Scoping and the national-rate-table exclusion are front-loaded, and the sibling redirect follows logically. The payment sentence is long and dense relative to its value, which costs a point.

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?

Output schema exists, yet the description still orients the agent with the returned fields, the pricing model, the row cap, and the key distinction from the national rate table. For a three-parameter, fully-described read tool, nothing material 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 drg, state, and max are already documented with format and defaults. The description only restates '3-digit DRG code and optional state; up to 20 rows,' adding no new semantics such as accepted code ranges or state-code behavior.

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 title and first sentence name the exact resource (CMS Medicare inpatient hospital averages per MS-DRG), list the dimensions returned, and explicitly distinguish the data from the IPPS national rate table. An agent can tell what this is without opening the schema.

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?

It states the required filter (3-digit DRG) plus optional state, the 20-row ceiling, and routes an adjacent need to health_medicare_advantage_star. It does not spell out when this tool is the wrong choice beyond that single redirect, so it falls short of full when/when-not coverage.

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.

Resources