Skip to main content
Glama

Med Bill Check: Draft a letter to a billing office for the user to send

medbillcheck_draft_bill_letter
Read-onlyIdempotent

Med Bill Check. Draft a letter to a billing office for the user to send. For requests like "help me dispute this bill", "write a letter asking for an itemized bill", "can I ask for a discount?" or "how do I apply for charity care?". Returns a letter as plain text with [brackets] for anything not given, tips, and the user's No Surprises Act and Good Faith Estimate rights with official CMS links. It never sends anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoBilling code of the charge. With amount, a dispute letter adds Medicare's benchmark (for a hospital charge, the hospital outpatient rate as well as the doctor's part).
dateNoDate of service.
nameNoPatient or account holder name.
typeYesType: itemized (ask for an itemized bill), dispute (ask for a charge to be reviewed), discount (prompt-pay or self-pay discount), or assistance (financial assistance or charity care).
stateNoUS state, used for the benchmark in a dispute letter.
amountNoAmount charged or balance due, in US dollars.
reasonNoA sentence on what the user wants checked, for a dispute letter.
accountNoAccount or invoice number on the bill.
insuredNoSet to no if paying without insurance (self-pay), for a discount letter.
serviceNoThe service in plain words.
settingNoSetting: office or facility (hospital or surgery center), for the benchmark in a dispute letter. ER visits and hospital clinic visits count as facility anyway.
providerNoHospital, clinic or provider name.
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. Changed3 schema fields changed
    • changedInput schema / properties / insured / description
      Previous value: -"no if paying without insurance (self-pay), for a discount letter."New value: +"Set to no if paying without insurance (self-pay), for a discount letter."
    • changedInput schema / properties / setting / description
      Previous value: -"office or facility (hospital or surgery center), for the benchmark in a dispute letter. ER visits and hospital clinic visits count as facility anyway."New value: +"Setting: office or facility (hospital or surgery center), for the benchmark in a dispute letter. ER visits and hospital clinic visits count as facility anyway."
    • changedInput schema / properties / type / description
      Previous value: -"itemized (ask for an itemized bill), dispute (ask for a charge to be reviewed), discount (prompt-pay or self-pay discount), or assistance (financial assistance or charity care)."New value: +"Type: itemized (ask for an itemized bill), dispute (ask for a charge to be reviewed), discount (prompt-pay or self-pay discount), or assistance (financial assistance or charity care)."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it discloses the return format (plain text with [brackets] for missing information), the content (tips and No Surprises Act/Good Faith Estimate rights with official CMS links), and explicitly states 'It never sends anything.' This reinforces the read-only and non-destructive hints with useful nuance.

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 front-loaded with the core action, followed by concrete usage examples and then return/behavior details. Every sentence is useful and there is no redundant or wasted text.

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 13 parameters, no output schema, and rich annotations, the description covers the purpose, trigger examples, output format, and safety behavior. An agent has everything needed to select and invoke the tool correctly.

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 description coverage is 100%, so all 13 parameters are well documented in the schema itself. The description adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: 'Draft a letter to a billing office for the user to send.' It is clearly distinct from sibling tools like check_price or search_services, but it does not explicitly name an alternative tool or draw a direct comparison.

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?

Four example user requests ('help me dispute this bill', 'write a letter asking for an itemized bill', etc.) give clear context for when to use this tool. However, there is no explicit guidance on when not to use it or which sibling tool to choose instead.

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.