Skip to main content
Glama

code_bundle_validator

[Taxonomy II.25 — baseline response (public data only)] Check a set of CPT codes against NCCI bundling rules (distinct from modifier-based unbundling).

WHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them.

WHEN NOT: For full bill scans (use scan_bill_for_errors). For appealing a coding-related denial (use generate_appeal_letter).

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": {
      "cpt_codes": "<cpt_codes>"
    },
    "name": "code_bundle_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpt_codesYesArray of CPT codes to check for NCCI bundling violations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations are not provided, so the description carries the full burden for behavioral transparency. 'Check' implies a read-only analysis, but the description does not disclose what the tool returns, whether it performs any side effects, or what output format the agent should expect.

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 description is well-structured with clear sections and no redundant fluff. It loses one point because the WHEN TO USE section includes broader code-related use cases that are not fully aligned with NCCI bundling checks.

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

Completeness2/5

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

The description covers input and basic usage boundaries, but there is no output schema and no description of the return value. An agent cannot tell whether the tool returns a boolean, a list of violations, or a structured report. It also does not distinguish itself from the sibling bundling_violation_detector.

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?

The schema already describes the sole parameter cpt_codes as an array of strings with full coverage. The description does not add substantive detail beyond the schema, so it meets the baseline but does not exceed it.

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 states a specific verb ('Check'), a specific resource ('CPT codes against NCCI bundling rules'), and a clear scope. It also distinguishes itself from modifier-based unbundling, making its purpose unambiguous.

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?

The WHEN TO USE and WHEN NOT sections provide some guidance, but the WHEN TO USE language is overbroad, including code lookup and mapping questions that more naturally belong to siblings like lookup_cpt or cpt_to_icd_mapper. It does not explicitly route users to those alternatives.

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