Skip to main content
Glama

Get a cost estimate

get_cost_estimate
Read-only

[Step 1 of cost_check]

Returns a general cost range and a link to the cost estimate page, pre-filled with the plan and service, where the family sees the exact amount for their plan.

Use when: A parent asks what care costs, about a copay, or whether a plan is covered.

Example: get_cost_estimate({ insurance: 'Aetna', service: 'adhd-testing' })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceNotherapy (the default), clinical-matching (unsure what is needed), medication (non-stimulant only), adhd-testing or autism-testing.
insuranceNoInsurance plan name, or "Cash Pay" for self-pay. A plan Emora does not take is ignored, and the result says so.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / insurance / description
      Previous value: -"The family's insurance plan. In-network plans: Cash Pay, Aetna, Anthem Blue Cross, Blue Cross Blue Shield, ChampVA, Cigna, Florida Blue, Magellan, Medical Mutual, United Healthcare, Optum, Oscar, Tricare, Tricare West, UMR. \"Cash Pay\" for self-pay. You may pass any plan: for one we're not in-network with, the tool drops the insurance filter and says so."New value: +"Insurance plan name, or \"Cash Pay\" for self-pay. A plan Emora does not take is ignored, and the result says so."
    • changedInput schema / properties / service / description
      Previous value: -"Which service. Pass the name, not a number:\n- therapy: Ongoing therapy for a child, teen or parent: anxiety, mood, behavior, school or family stress, parent training (PCIT). The default when nothing points elsewhere.\n- clinical-matching: A 45-minute virtual intake where a clinician works out the right care and the right clinician. For families who aren't sure what they need or don't want to pick. Billed like any visit; never call it free.\n- medication: A psychiatric evaluation and ongoing medication care, when a family or pediatrician is asking about medication. Non-stimulant medications only: Emora never prescribes stimulants or controlled substances.\n- adhd-testing: A psychologist-led ADHD evaluation for a diagnosis (focus, impulsivity, hyperactivity), e.g. when a teacher or pediatrician suggests getting evaluated for ADHD.\n- autism-testing: A psychologist-led autism (ASD) evaluation for a diagnosis (social communication, repetitive behaviors, sensory needs). Evaluation only: Emora does not provide ABA therapy.\nNumeric appointment-type IDs are still accepted.\nPass it when known: the estimate page opens on that service."New value: +"therapy (the default), clinical-matching (unsure what is needed), medication (non-stimulant only), adhd-testing or autism-testing."
    • changedInput schema / properties / service / enum
      Previous value: -[
      -  "354092",
      -  "446840",
      -  "446841",
      -  "449671",
      -  "465593",
      -  "therapy",
      -  "clinical-matching",
      -  "medication",
      -  "adhd-testing",
      -  "autism-testing"
      -]New value: +[
      +  "therapy",
      +  "clinical-matching",
      +  "medication",
      +  "adhd-testing",
      +  "autism-testing"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / insurance / description
      Added value: +"The family's insurance plan. In-network plans: Cash Pay, Aetna, Anthem Blue Cross, Blue Cross Blue Shield, ChampVA, Cigna, Florida Blue, Magellan, Medical Mutual, United Healthcare, Optum, Oscar, Tricare, Tricare West, UMR. \"Cash Pay\" for self-pay. You may pass any plan: for one we're not in-network with, the tool drops the insurance filter and says so."
    • removedInput schema / properties / insurance / enum
      Removed value: -[
      -  "Cash Pay",
      -  "Aetna",
      -  "Anthem Blue Cross",
      -  "Blue Cross Blue Shield",
      -  "ChampVA",
      -  "Cigna",
      -  "Florida Blue",
      -  "Magellan",
      -  "Medical Mutual",
      -  "United Healthcare",
      -  "Optum",
      -  "Oscar",
      -  "Tricare",
      -  "Tricare West",
      -  "UMR"
      -]
    • addedInput schema / properties / service / description
      Added value: +"Which service. Pass the name, not a number:\n- therapy: Ongoing therapy for a child, teen or parent: anxiety, mood, behavior, school or family stress, parent training (PCIT). The default when nothing points elsewhere.\n- clinical-matching: A 45-minute virtual intake where a clinician works out the right care and the right clinician. For families who aren't sure what they need or don't want to pick. Billed like any visit; never call it free.\n- medication: A psychiatric evaluation and ongoing medication care, when a family or pediatrician is asking about medication. Non-stimulant medications only: Emora never prescribes stimulants or controlled substances.\n- adhd-testing: A psychologist-led ADHD evaluation for a diagnosis (focus, impulsivity, hyperactivity), e.g. when a teacher or pediatrician suggests getting evaluated for ADHD.\n- autism-testing: A psychologist-led autism (ASD) evaluation for a diagnosis (social communication, repetitive behaviors, sensory needs). Evaluation only: Emora does not provide ABA therapy.\nNumeric appointment-type IDs are still accepted.\nPass it when known: the estimate page opens on that service."
    • changedInput schema / properties / service / enum
      Previous value: -[
      -  "354092",
      -  "446840",
      -  "446841",
      -  "449671",
      -  "465593"
      -]New value: +[
      +  "354092",
      +  "446840",
      +  "446841",
      +  "449671",
      +  "465593",
      +  "therapy",
      +  "clinical-matching",
      +  "medication",
      +  "adhd-testing",
      +  "autism-testing"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / insurance / enum
      Previous value: -[
      -  "Cash Pay",
      -  "Aetna",
      -  "Anthem Blue Cross",
      -  "Baylor Scott & White",
      -  "Blue Cross Blue Shield",
      -  "ChampVA",
      -  "Cigna",
      -  "Florida Blue",
      -  "Magellan",
      -  "Medical Mutual",
      -  "United Healthcare",
      -  "Optum",
      -  "Oscar",
      -  "Tricare",
      -  "Tricare West",
      -  "UMR"
      -]New value: +[
      +  "Cash Pay",
      +  "Aetna",
      +  "Anthem Blue Cross",
      +  "Blue Cross Blue Shield",
      +  "ChampVA",
      +  "Cigna",
      +  "Florida Blue",
      +  "Magellan",
      +  "Medical Mutual",
      +  "United Healthcare",
      +  "Optum",
      +  "Oscar",
      +  "Tricare",
      +  "Tricare West",
      +  "UMR"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / insurance / enum
      Previous value: -[
      -  "Cash Pay",
      -  "Aetna",
      -  "Anthem Blue Cross",
      -  "Baylor Scott & White",
      -  "Blue Cross Blue Shield",
      -  "ChampVA",
      -  "Cigna",
      -  "Florida Blue",
      -  "Magellan",
      -  "United Healthcare",
      -  "Optum",
      -  "Oscar",
      -  "Tricare",
      -  "Tricare West",
      -  "UMR"
      -]New value: +[
      +  "Cash Pay",
      +  "Aetna",
      +  "Anthem Blue Cross",
      +  "Baylor Scott & White",
      +  "Blue Cross Blue Shield",
      +  "ChampVA",
      +  "Cigna",
      +  "Florida Blue",
      +  "Magellan",
      +  "Medical Mutual",
      +  "United Healthcare",
      +  "Optum",
      +  "Oscar",
      +  "Tricare",
      +  "Tricare West",
      +  "UMR"
      +]
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / service / enum
      Previous value: -[
      -  "354092",
      -  "446840",
      -  "465593",
      -  "446841",
      -  "449671"
      -]New value: +[
      +  "354092",
      +  "446840",
      +  "446841",
      +  "449671",
      +  "465593"
      +]
  7. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's added value is in disclosing what is actually returned: a general range rather than an exact figure, plus a pre-filled link where the family sees the precise amount. That distinction (estimate here, exact amount off-tool) is important behavior an agent would otherwise assume wrongly.

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?

Front-loaded step marker, then what it returns, then when to use it, then a one-line example. Every sentence earns its place; the range-versus-exact-amount contrast is the one piece of non-obvious information and it is stated crisply.

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 by describing both the range and the link artifact. Parameters are sparse (2, none required) and fully covered by the schema, so the only modest gap is not spelling out the step-2 handoff implied by 'cost_check'.

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% — both parameters carry descriptions and the service enum lists all five valid values, so the schema does the heavy lifting. The description adds only a single worked example using 'Aetna' and 'adhd-testing', which illustrates typical values but adds no semantics beyond what the schema already documents.

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 ('Returns a general cost range and a link to the cost estimate page'), plus the scope and pre-fill behavior. The '[Step 1 of cost_check]' marker and the cost-focused framing cleanly separate it from siblings like get_availability, get_booking_link, and search_providers, which handle scheduling and search rather than pricing.

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 'Use when: A parent asks what care costs, about a copay, or whether a plan is covered' line gives concrete triggering intents. It does not name an alternative tool or state a when-not condition, but the step marker implies a follow-on 'cost_check' action and the intent coverage is unambiguous.

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.

Resources