Skip to main content
Glama

What a HCPCS billing code is

hcpcs_lookup
Read-onlyIdempotent

What a HCPCS Level II code on a bill, supplier invoice or explanation of benefits describes (a letter and four digits, e.g. E0601, J9271, A4253), with its Medicare coverage status, from CMS's quarterly HCPCS file. CPT codes (five digits) are not covered: their descriptions are copyrighted.

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": {
      "code": "<code>"
    },
    "name": "hcpcs_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesHCPCS Level II code, e.g. E0601.

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?

While annotations cover safety (readOnlyHint), the description adds valuable contextual behavior by citing the source (CMS's quarterly file) and the inherent limitation regarding CPT codes. This adds data provenance which is helpful for AI agents.

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 description is extremely efficient, using one dense paragraph to cover definition, scope, constraints, and data source. There is zero waste in the writing.

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?

Given the tool is a lookup function, the definition provides all necessary boundaries: what it looks for (codes), what it returns (description/coverage), where the data comes from (CMS), and what it excludes (CPT).

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 coverage is 100%, establishing a baseline of 3. The description reinforces the format constraints and provides concrete examples like E0601, which confirms the schema's pattern requirement.

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 description is highly specific, stating it looks up the description and Medicare coverage status of HCPCS Level II codes. It clearly defines the scope by listing allowed formats (letter and four digits).

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?

The description provides strong usage context by listing where the codes appear (bills, invoices, EOB). It also serves as a usage exclusion by explicitly stating that CPT codes are not covered by this tool.

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