Skip to main content
Glama

Out-of-pocket estimate from your own dental plan figures

insurance_out_of_pocket
Read-only

Use this when the user has a private dental plan or a Medicare Advantage plan with dental benefits, knows its figures (deductible left, annual maximum left, coinsurance per procedure or per class), and asks what they would still pay for dental work in a US state. Every plan parameter comes from the user; the tool assumes none and names no insurer. Returns, per line, the state cash band (observed or estimated badge; the national band for crown, veneer, braces and dentures, whose per-state figures are not published here) and an estimated split (deductible, plan share, user share) on the low, average and high of the band, with the formula written out; a line missing a parameter is not computed and says which one. Phrasings: "my plan has 50 dollars of deductible left and 1,200 of annual max, coinsurance 50% on crowns, what would a crown in Ohio leave me to pay", "estimate my share for a root canal and a crown with my Medicare Advantage dental benefit in Florida", "¿cuánto me tocaría pagar por un implante con mi seguro dental si me quedan 800 del máximo anual?", "¿cuál sería mi parte de una endodoncia con coaseguro del 20% en Texas?". Do not use for: diagnosis, treatment choice, a named insurer's plan price, dentist recommendations, countries other than the US and Canada. Market research and public program data with a source URL and period on every figure; not a quote, not medical advice.

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": {
      "state": "<state>",
      "coverage": "<coverage>",
      "lines": "<lines>"
    },
    "name": "insurance_out_of_pocket"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoResponse language for labels/notes: "en" (default) or "es".en
linesYesLines in the order the user expects them to be billed (1-10).
stateYesTwo-letter US state code (or DC). One of: AL, AR, MS, KY, WV, IA, KS, OK, IN, SD, LA, NE, SC, GA, MO, TN, ND, OH, NC, MI, NM, WI, UT, ID, MN, TX, WY, AZ, FL, MT, CO, VA, IL, ME, PA, CT, OR, VT, DE, NV, RI, MD, WA, NH, NJ, MA, DC, AK, HI, NY, CA.
coverageYesCoverage category only (no plan or insurer name).
no_annual_maximumNotrue only if the user's plan document states no annual maximum.
coinsurance_by_classNoThe user's coinsurance in percent per class label they provide, e.g. their plan's own class names.
annual_max_remaining_usdNoAnnual maximum still available this benefit year, in US dollars. Required unless no_annual_maximum is true.
deductible_remaining_usdNoDeductible still to meet this benefit year, in US dollars (0 if met). Required to compute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag a safe read-only, non-open-world operation; the description adds substantial behavioral context: no assumed plan values, observed/estimated bands, formula written out, and uncomputed lines reported with the missing parameter. This is well beyond what the annotations provide.

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?

It front-loads the usage condition and keeps the return behavior in a compact block, but the four example phrasings and the do-not-use/provenance caveats make it longer than necessary. The length is still defensible for an 8-parameter nested tool.

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?

For a complex, read-only estimator with no output schema, the description explains the returned bands, badges, splits, formula, and missing-parameter behavior well. The only notable completeness flaw is the "US and Canada" exclusion line, which conflicts with the schema's US-only state enum.

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 coverage is 100%, and the schema already documents all eight parameters in detail. The description reinforces the user-supplied plan inputs and gives examples, but adds little parameter-level syntax or constraints beyond the schema.

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 opening sentence states the specific estimate and the exact precondition: user-supplied deductible, annual max, and coinsurance figures for a US state. It also rules out named-insurer quotes and medical advice, so an agent can separate this from the benchmark and state-cost siblings.

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?

It gives explicit "Use this when" criteria and a "Do not use for" list, plus representative phrasings. It does not name alternative sibling tools for cases like missing plan figures, and the "US and Canada" exclusion line is potentially inconsistent with the schema's US-only state enum.

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.