Skip to main content
Glama

HCPCS Level II billing code search: code and short

health_cpt_hcpcs_procedure
Read-only

HCPCS Level II billing code search (CMS code set, via NLM Clinical Tables): code and short description for procedures, supplies and drugs, with total match count. CPT codes are AMA-licensed and not included. Up to 20 codes per call. 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": {
      "term": "<term>"
    },
    "name": "health_cpt_hcpcs_procedure"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many codes, 1 to 20 (default 10)
termYesWords to search in HCPCS descriptions, 2 to 60 characters

Output Schema

NameRequiredDescriptionDefault
termNo
codesNo
totalNo
sourceNo
checkedAtNo

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 only declare readOnlyHint and openWorldHint, but the description adds real behavioral detail the annotations do not: the upstream source (CMS via NLM Clinical Tables), a per-call cap of 20 codes, the total match count in the response, and a pay-per-call model with failed calls uncharged. It does not discuss rate limits, pagination, or what happens past the 20-code cap.

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?

Front-loaded with the core capability, then exclusions, then limits, then cost — every clause carries distinct information and no sentence merely restates the tool name or schema.

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 simple two-parameter read tool with an output schema and existing safety annotations, the description supplies the essential extras: data provenance, coverage exclusions, result cap, and pricing. Only edge-case behavior (cap overflow, empty results) is unaddressed.

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 both parameters are already fully documented, making 3 the baseline. The description only weakly reinforces the `max` bound with "up to 20 codes per call" and adds nothing about term syntax such as matching behavior or wildcards.

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 and resource ("HCPCS Level II billing code search"), names the exact scope (procedures, supplies, drugs), and explicitly carves out CPT codes as excluded and AMA-licensed — an agent can tell immediately what it does and does not cover.

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?

Gives clear context for when to use it (searching HCPCS Level II descriptions) and a useful negative boundary that CPT lookups are out of scope. It stops short of naming a concrete alternative tool for CPT lookup, so the routing is implied rather than explicit.

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