Skip to main content
Glama

medical-bill-auditor

Medical Bill Upcoding & Overcharge Slasher — Paste an itemized hospital or physician bill and get a decision first: dispute it or not, the estimated dollars above a defensible price, and a dispute letter ready to send. Flags E/M upcoding, NCCI unbundling, duplicates and unit errors line by line, prices professional claims against the CMS physician fee schedule, checks the No Surprises Act self-pay dispute deadline, and lists the letter's pla

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": {
      "facilityType": "<facilityType>"
    },
    "name": "medical-bill-auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
billTextNoAlternative to lineItems: paste the itemized bill, one line item per line, e.g. "99285 EMERGENCY DEPT VISIT LVL 5 1 $3,250.00". Lines with a CPT/HCPCS code and a dollar amount are read in code; send exactly one of lineItems or billText.
coverageNoDetermines which No Surprises Act protections can apply.
claimTypeNoPhysician (CMS-1500) or hospital/facility (UB-04) bill. Medicare physician fee schedule benchmarks apply only to professional claims.
lineItemsNo
patientNameNo
facilityNameNo
facilityTypeYes
patientStateNo
visitSummaryNoWhat actually happened: symptoms, duration, tests, treatment.
accountNumberNo
billReceivedDateNoDate the initial bill was received; used for the 120-day dispute deadline.
goodFaithEstimateAmountNoGood Faith Estimate received (self-pay).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses the analytic checks performed, the benchmarking source (CMS physician fee schedule, professional claims only), and the No Surprises Act deadline check. It also describes the return payload (decision, dollar delta, letter). The clear defect is the truncated final clause 'lists the letter's pla', which leaves the letter's components unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and capability list are front-loaded, which is correct, but the body is a single dense run-on sentence stacking six separate capabilities. The text also terminates mid-word, so the final sentence never earns its place and instead introduces confusion about what the dispute letter contains.

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

Completeness3/5

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

This is a complex tool with 12 parameters, no annotations, and no output schema, so the description must do heavy lifting. It explains the analytical outputs well but leaves the required facilityType input and roughly half the parameters undocumented, and the truncated ending means the advertised dispute-letter output is incompletely specified.

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?

With 12 parameters and only 50% schema description coverage, the description compensates for some of the gap by explaining that coverage drives No Surprises Act applicability, that claimType selects CMS physician fee schedule benchmarking, and that billText is a paste alternative to lineItems. However, the single required parameter, facilityType, is never mentioned, and most of the remaining fields (patientState, visitSummary, goodFaithEstimateAmount, billReceivedDate) receive no explanation in either the description or a schema description.

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 names a specific verb and resource: paste an itemized hospital or physician bill and receive a dispute-or-not decision, an estimated overcharge dollar amount, and a ready-to-send dispute letter. It also enumerates the concrete detection capabilities (E/M upcoding, NCCI unbundling, duplicates, unit errors), so an agent knows exactly what class of task this tool serves.

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 usage context is clear: it is for an itemized bill you want audited, and it tells the agent the output is a dispute decision plus a letter. The schema-side note that lineItems and billText are mutually exclusive alternatives adds routing guidance. It stops short of naming when not to use it or pointing to a sibling tool, so it is not a 5.

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