Skip to main content
Glama

Dental cost by US state

dental_cost_by_state
Read-only

Use this when the user asks what a dental procedure costs in a given US state (51 incl. DC), or how a state sits next to the US average, for one of 12 procedures: exam and cleaning, filling, deep cleaning, extraction, root canal, crown, implant, All-on-4, dentures, braces, veneer, whitening. Returns the state cash band (low / average / high) in US dollars, the national band, the gap in percent and the state's Restorative Cost Index. For crown, veneer, braces and dentures it returns no state figure: those per-state figures (ASQ360/CareCredit Average Procedural Cost Study 2023-2024) are cited on realdentalcosts.com pages but not licensed for redistribution, so the answer gives status no_source_at_this_level, the study link and the national band. Each figure is labelled observed or estimated, with a note naming the study behind it and its period (implants from Real Dental Costs' editorial estimate, edition 2026.1, DOI 10.5281/zenodo.20531728, not collected data, state ranking validated against ASQ360, levels not verified; other procedures scaled from the national figure and marked estimated), so the answer can say where the state number comes from and how old it is. Phrasings: "how much is a filling in Ohio without insurance", "what do people in Florida pay for a root canal", "¿cuánto cuesta un implante dental en Texas?", "costo de una limpieza dental en California". When the user already has an amount quoted by their dentist and asks whether it is normal, use benchmark_treatment_plan instead: it places the quoted amount against this band line by line. 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": {
      "procedure": "<procedure>",
      "state": "<state>"
    },
    "name": "dental_cost_by_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoResponse language for labels/notes: "en" (default) or "es".en
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.
procedureYesProcedure id. One of: exam (Exam, cleaning & X-rays), filling (Composite filling (1 tooth)), deepclean (Deep cleaning (SRP, per quadrant)), extraction (Tooth extraction), rootcanal (Root canal), allon4 (All-on-4 (per arch)), whitening (Professional teeth whitening), crown (Dental crown), veneer (Porcelain veneer (per tooth)), braces (Braces (traditional, full case)), implant (Single dental implant (complete)), dentures (Full set of dentures (both arches)).
quoted_usdNoOptional amount quoted to the user for this procedure, in US dollars, in the unit of the procedure label (per tooth, per arch, full set): returns its position in the state band.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / quoted_usd
      Added value: +{
      +  "description": "Optional amount quoted to the user for this procedure, in US dollars, in the unit of the procedure label (per tooth, per arch, full set): returns its position in the state band.",
      +  "maximum": 500000,
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say read-only and closed-world; the description goes much further by disclosing the licensing restriction that suppresses state figures for crown/veneer/braces/dentures and the resulting no_source_at_this_level status, plus observed-vs-estimated labelling, the underlying study and period, and the DOI. That is exactly the behavioral context an agent needs to relay a caveat rather than invent a number.

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 the trigger and the return shape before the caveats, and the long source/licensing passage is load-bearing rather than filler. It is still a very dense single block, and the four example phrasings plus provenance detail make it heavier than the routing decisions require.

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 does the work of explaining return fields, the no-source status, and figure provenance, which is enough to call it correctly. The one loose end is the unmentioned quoted_usd input, whose existence conflicts with the instruction to send quoted amounts to benchmark_treatment_plan.

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% and enum labels are documented, so the description only needs to add meaning; it does so by expanding procedure ids into plain-language procedures and by flagging which procedure values have no per-state data. The gap is quoted_usd: the schema accepts it and says it returns the amount's position in the band, yet the description never mentions it and instead routes quote-checking to benchmark_treatment_plan, leaving that parameter's role ambiguous.

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+resource (returns dental procedure cost bands for a US state) plus the exact shape of the answer: state cash band low/average/high, national band, percent gap, and Restorative Cost Index. It also carves out four procedures where no state figure is returned, which distinguishes it from the national-average and comparison siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggers (user asks what a procedure costs in a state, or how a state compares to the US average), names the alternative for a different case (benchmark_treatment_plan when the user has a dentist's quote), and lists explicit exclusions (diagnosis, treatment choice, insurer plan prices, dentist recommendations, non-US/Canada).

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.