Skip to main content
Glama

Find surgery-center vs. hospital costs and specialists

find_care
Read-only

For a person with Original Medicare (not Medicare Advantage), compare what a procedure costs them at an outpatient surgery center versus a hospital in their county, any SaveWell reward with a Medigap plan, and SaveWell-network specialists within 30 miles of their ZIP code. Costs are estimates based on Medicare claims for the patient's county, not a quote; the Part B deductible may apply. The patient may choose any qualified provider. SaveWell's specialists are a recommendation, not a requirement. Choosing a setting is a decision for the patient and their doctor. Present these figures as cost information, not medical advice. SaveWell works with Original Medicare only, not Medicare Advantage. Whether a specific Medigap plan qualifies for the reward should be confirmed with a care guide.

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>",
      "zip": "<zip>"
    },
    "name": "find_care"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesThe patient's 5-digit ZIP code.
coverageNo'medigap' if the patient has a Medicare Supplement (Medigap) plan.medicare_only
procedureYesProcedure id from list_procedures, e.g. 'colonoscopy'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description goes further by disclosing data provenance and limits: estimates from Medicare claims rather than a quote, the Part B deductible possibly applying, and that specialists are recommendations rather than requirements. It does not describe the response shape or what happens when a procedure has no data in the county, which keeps it below a 5 given the low annotation burden already covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core comparison is correctly front-loaded in sentence one, but roughly half the text is near-duplicative disclaimer language ('recommendation, not a requirement', 'may choose any qualified provider', 'a decision for the patient and their doctor', 'not medical advice') that does not help an agent select or invoke the tool. It could be trimmed substantially without losing selection signal.

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 read-only, 3-parameter tool with full schema coverage and no output schema, the description covers eligibility, output content, and interpretive caveats well. Gaps are minor: nothing about behavior for an invalid procedure id or a ZIP outside SaveWell's coverage area.

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: 'within 30 miles of their ZIP code' quantifies the radius the schema omits, 'in their county' explains how ZIP resolves geographically, and 'any SaveWell reward with a Medigap plan' explains what the coverage enum unlocks. Only the procedure parameter's dependence on list_procedures is left to 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 description opens with a specific verb and a precisely scoped set of resources: comparing outpatient surgery center vs. hospital procedure costs, SaveWell Medigap rewards, and in-network specialists within 30 miles. This is clearly distinct from the only sibling, list_procedures, which is a lookup tool. An agent knows exactly what this returns without opening the schema.

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 states a clear eligibility gate ('For a person with Original Medicare (not Medicare Advantage)') and repeats the exclusion at the end, plus tells the agent how to frame results (cost information, not medical advice, confirm Medigap qualification with a care guide). It never explicitly routes to list_procedures for obtaining the procedure id, though the schema covers that.

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