Skip to main content
Glama

Check several lines of an itemized bill at once

check_whole_bill
Read-onlyIdempotent

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.3/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds substantial non-schema behavior: what is returned (per-line Medicare comparison, totals, questions_to_ask with the specific categories flagged), and the special handling for hospital/facility lines with the compared_with field. This is meaningful disclosure beyond the annotations.

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?

Purpose is front-loaded and every sentence carries information, but the third sentence is a long run-on enumerating questions_to_ask categories, and the second sentence embeds a verbose quoted example. It is dense but slightly sprawling.

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?

With no output schema, the description must carry the return-value burden, and it does: it names the returned comparison, totals, and questions_to_ask contents. The facility vs. office comparison logic and the compared_with annotation are also explained, leaving nothing an agent needs to call it correctly.

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 meaning: it explains the lines syntax (code, optional x and units, then amount) and how setting/facility lines are treated, including that omitted billed_by compares against both together. That exceeds what the schema alone conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (check) and resource (several lines of an itemized bill) with the scope 'at once', which implies batch vs. the sibling check_price. It never names the sibling outright, so differentiation from check_price relies on inference from 'several lines at once'.

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 'For when someone reads out or pastes several lines...' clause plus a concrete example gives a clear usage context. It stops short of explicit exclusions or named alternatives (e.g., 'for a single code use check_price'), so it does not reach the 5 bar.

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.