Skip to main content
Glama

Medicare Physician Payment

medicare_physician_payment
Read-onlyIdempotent

What does Medicare pay a doctor for a procedure code, in a specific place? Returns the relative value units (work, practice expense, malpractice) and the actual dollar payment for a HCPCS/CPT code, adjusted for the Medicare LOCALITY — payment varies geographically, not just by state. Answers "how much does Medicare pay for 99213", "what is code 27130 worth in Los Angeles", "reimbursement rate for an office visit in Texas", and fee-schedule or contract-rate benchmarking. Gives both the facility and non-facility amount (a procedure pays less in a hospital, because the hospital bills the overhead separately), the global period, the status code saying whether the code is separately payable at all, and for CMS-owned HCPCS Level II codes (G, J, A, etc.) the CMS short descriptor (CPT descriptions are AMA copyright and are not returned). States the fee-schedule YEAR and the locality it resolved to on every response, because a rate quoted for the wrong year or locality is a wrong number. Sourced from the CMS Physician Fee Schedule relative value files.

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": {
      "code": "99213",
      "locality": "CA"
    },
    "name": "medicare_physician_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesHCPCS or CPT code, e.g. "99213" (office visit) or "27130" (hip replacement).
yearNoFee-schedule year, e.g. 2026. Omit to use the newest loaded year, which is stated in the response.
localityNoWhere the service is provided — a state code ("CA"), state name, or Medicare locality name ("Bakersfield", "Manhattan"). Payment varies by locality; omit only if you want the national picture.
modifierNoOptional HCPCS modifier, e.g. "26" (professional component) or "TC" (technical component).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, and the description goes well beyond them: it states that the resolved fee-schedule year and locality are echoed on every response, that both facility and non-facility amounts are returned, and that CPT descriptors are omitted for AMA copyright reasons while CMS Level II short descriptors are included. These are non-obvious return-shape caveats an agent could not infer from the 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?

The core question is front-loaded and the sentence order moves from answer to output fields to caveats, which is sound. It is dense and slightly longer than necessary — the quoted example questions repeat the same point three ways — but no sentence is off-topic.

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?

With no output schema, the description carries the return-value burden and does so fully: it names each returned field, explains the facility/non-facility split and its cause, flags the copyright limitation on descriptors, and notes that year and locality are echoed. Nothing an agent needs 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds rationale the schema lacks — that locality is a real payment driver rather than a state-only filter, and that a wrong year or locality silently yields a wrong number, explaining why 'year' defaults to the newest loaded schedule. The modifier parameter is left to the 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?

Opens with a precise verb+resource framing (what Medicare pays for a procedure code in a specific place) and enumerates the returned quantities: work/PE/malpractice RVUs, dollar payment, facility vs non-facility amounts, global period and status code. An agent can distinguish this from rate-lookup siblings 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?

Concrete usage contexts are given via example queries (office visit, hip replacement, Texas office visit) and the benchmarking use case, so the agent knows the situations this tool serves. It stops short of naming sibling alternatives such as medicare_opps_rate or medicare_dmepos_rate or stating exclusions, which keeps it below a 5.

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.