Skip to main content
Glama

Med Bill Check: Check several lines of an itemized bill at once

medbillcheck_check_whole_bill
Read-onlyIdempotent

Med Bill Check. Check several lines of an itemized bill at once. For when someone reads out or pastes several lines from an itemized bill, for example "my ER bill has 99284 for $2,500, 85025 twice for $120 and 36415 three times, does anything look off?". Takes the lines as code, optional x and units, then the amount. Returns each line against Medicare's rate, totals, and questions_to_ask: repeated codes, units above Medicare's automated daily limit, the highest visit levels, hospital clinic facility fees and charges far above what providers typically bill. Lines of a hospital bill (any bill with an ER visit on it, or setting=facility) are compared with Medicare's hospital outpatient rate plus the doctor's part; each such line says compared_with.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity, for big cities with their own Medicare rates.
linesYesUp to 15 bill lines separated by commas: code, then x and units if more than one, then the amount. Example: 99284:2500, 85025x2:120, 36415:45.
stateNoUS state name or two-letter code.
settingNoSetting: office or facility. Leave out if not known.
billed_byNoWhose bill the charge is on when the service was in a hospital: hospital (the hospital's own facility charge) or doctor (the doctor's or physician group's bill). Leave out if not known: the charge is then compared with both together.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / setting / description
      Previous value: -"office or facility. Leave out if not known."New value: +"Setting: office or facility. Leave out if not known."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: it discloses the Medicare-rate comparison basis, the special handling of hospital bills (facility rate plus doctor's part) and the per-line compared_with field, and the specific output content (each line, totals, questions_to_ask). That is rich behavioral context an agent cannot get from structured fields.

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 purpose, then usage, then input format, then return behavior. The long quoted example is illustrative but costs space; a shorter example would earn the same clarity. Overall every sentence carries 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?

With no output schema, the description carries the return-value burden and does so adequately (per-line Medicare comparison, totals, questions_to_ask). It omits any mention of rate-limiting or error behavior for malformed line strings, which is a minor gap for a 5-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: the positional 'code, optional x and units, then the amount' ordering, the <=15 line cap interpretation, and the default behavior of billed_by when omitted ('compared with both together').

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 ('Check several lines of an itemized bill at once') and scopes it to batch line checking, which cleanly separates it from medbillcheck_check_price (single price) and medbillcheck_search_services. The example of the ER bill makes the intended input shape concrete.

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?

Explicitly says when to use it: someone reads out or pastes several lines from an itemized bill. It doesn't name the sibling (check_price) or state when not to use it, so it stops just short of full routing guidance.

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.