Skip to main content
Glama

List Medicare documentation requirements for a DME code

get_documentation_requirements
Read-onlyIdempotent

For one DME HCPCS code and date of service, list the governing LCD and policy article names, CMS links, section headings, and how many requirements are extracted. An anonymous caller also gets one sample requirement. The rest of the passage text, and the denial sentences, require a plan that includes receipts, which also adds source proof: the archived file, the quote's position, the SHA-256, and the capture date. Returns an explicit gap when nothing is extracted. 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>"
    },
    "name": "get_documentation_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
hcpcsYesHCPCS Level II code, e.g. E0601 (CPAP), K0001 (wheelchair)
stateNoTwo-letter US state, e.g. CO. Optional.
date_of_serviceNoYYYY-MM-DD. Defaults to today.

Output Schema

NameRequiredDescriptionDefault
gapNo
hcpcsYes
stateNo
servedYes
denialsYes
documentsYes
requirementsYes
date_of_serviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the read-only/idempotent annotations: it discloses the tiering behavior (anonymous callers receive only one sample requirement), what the paid tier unlocks (remaining passage text, denial sentences, archived file, quote position, SHA-256, capture date), and that an explicit gap is returned when nothing is extracted. That is exactly the kind of hidden behavioral context annotations cannot convey.

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-loaded with the outcome first, then access tiers, then constraints — efficient overall. The middle sentence ('The rest of the passage text, and the denial sentences, require a plan that includes receipts...') is slightly convoluted but each sentence still carries distinct information.

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

Completeness4/5

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

For a read-only lookup with an output schema, the description covers purpose, access gating, provenance fields, and empty-result behavior. The only omission is any mention of the optional state parameter's effect on results, which is minor given the schema documents it.

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 hcpcs, state, and date_of_service are already documented with patterns and examples. The description reinforces the hcpcs/date-of-service inputs but adds no syntax or semantics beyond the schema, and never mentions the optional state parameter. Baseline 3 applies.

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?

Opens with a precise verb+resource+scope: 'For one DME HCPCS code and date of service, list the governing LCD and policy article names, CMS links, section headings, and how many requirements are extracted.' That is far more specific than the name alone. It does not explicitly name check_dme_coverage as the sibling it differs from, so an agent must infer the coverage-vs-documentation boundary.

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?

Usage is implied by 'for one DME HCPCS code and date of service' and the description clearly explains the anonymous-vs-plan access tiers, but it never says when to prefer this over check_dme_coverage or the other siblings, nor any exclusions beyond 'codes only, no patient data.'

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