Skip to main content
Glama

Check Medicare DME coverage for a HCPCS code

check_dme_coverage
Read-onlyIdempotent

Look up Medicare coverage for one durable medical equipment (DME) HCPCS Level II code in a US state on a date of service. Returns the Local Coverage Determination (LCD) and policy articles in force on that date with CMS links, whether the code is on the Medicare prior authorization list, and the documentation-requirements status. Medicare fee-for-service DME only. Does not decide whether a specific claim will be paid. Codes only, no patient data.

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": {
      "hcpcs": "<hcpcs>",
      "state": "<state>"
    },
    "name": "check_dme_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
hcpcsYesHCPCS Level II code, e.g. E0601 (CPAP), K0001 (wheelchair)
stateYesTwo-letter US state of the beneficiary or supplier, e.g. CO
date_of_serviceNoYYYY-MM-DD. Defaults to today.

Output Schema

NameRequiredDescriptionDefault
hcpcsYes
stateNo
receiptNo
upgradeYes
citationYes
coverageYes
governingYes
descriptorNo
date_of_serviceYes
prior_authorizationNo
documentation_requirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world profile, so the bar is lower. The description still adds real context beyond them: what the result contains (LCD and policy articles in force on the date, prior authorization list status, documentation-requirements status) and the no-claim-adjudication caveat. It omits only minor traits like latency or coverage gaps outside FFS.

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 purpose and constraints are front-loaded in the first two sentences, and the remaining sentences strip away ambiguity in a few words each. No filler or repetition of schema content.

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 an output schema present, the description need not describe return values, yet it still summarizes them at a useful level. Annotations plus 100% parameter coverage plus the explicit FFS/no-claim caveats leave nothing an agent needs missing before calling.

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 hcpcs, state, and date_of_service with patterns and examples. The description reinforces that only a single code is accepted and that the date determines which policy is in force, but adds no format or domain nuance beyond 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?

States a specific verb (look up), resource (Medicare coverage for one DME HCPCS Level II code), and scope qualifiers (US state, date of service). Explicitly narrows to Medicare fee-for-service DME, which separates it from the broader siblings like search and fetch.

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?

Clear about scope and boundaries: 'Medicare fee-for-service DME only' and 'Does not decide whether a specific claim will be paid' tell the agent when this tool is not appropriate. It stops short of naming alternatives such as get_documentation_requirements for follow-up detail, so routing is only partly resolved.

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