Skip to main content
Glama

Hospital Price Compare

hospital_price_compare
Read-onlyIdempotent

Side-by-side prices for one service at up to 10 named hospitals (by CMS Certification Number, CCN, from hospital_price_search or hospital_price_coverage). Same fields and same labelling as hospital_price_search: gross charge vs self-pay cash vs payer-negotiated rates, dollar_available on every negotiated rate, and for each hospital that has no price a stated reason (not held and why / code absent / payer not listed). Use for "compare MS-DRG 470 at these three hospitals for Blue Cross".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ccns": [
        "140208",
        "140179",
        "140054"
      ],
      "code": "90853",
      "payer": "blue cross",
      "rates_per_hospital": 2
    },
    "name": "hospital_price_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccnsYesCMS Certification Numbers (6 characters, e.g. "330101"), 1-10.
codeYesThe service code: a CPT/HCPCS code from the CMS 70 shoppable services (e.g. "70450" head CT, "45378" colonoscopy, "99213"-style E&M codes only where on that list) or an MS-DRG number (e.g. "470" major joint replacement).
planNoCase-insensitive substring of the plan name.
payerNoCase-insensitive substring of the payer name.
settingNoRestrict to inpatient or outpatient pricing.
code_typeNoOptional. Inferred when omitted: 1-3 digits is an MS-DRG, a 5-character code is CPT/HCPCS.
rates_per_hospitalNoNegotiated rows per hospital (1-25, default 25).

Output Schema

NameRequiredDescriptionDefault
codeNoCode
hintNoHow to narrow or fix the request
foundNoWhether at least one priced result was found
pricedNoHospitals with a price
reasonNoMachine-readable reason when found is false
sourceNoPublisher and dataset
messageNoPlain-language explanation of the reason
coverageNoWhich states and how many hospitals the store holds
code_typeNoMS-DRG or CPT/HCPCS
hospitalsNoHospitals with their prices or absence reasons
requestedNoCCNs requested
data_as_ofNoFile last-updated date, or the store cycle
licence_noteNoReuse-licence caveat

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare the safety profile, and the description adds meaningful behavioral context: the 10-hospital cap, the price categories returned, dollar_available on negotiated rates, and stated reasons when a hospital has no price. These details help the agent understand the comparison output without contradicting any annotation.

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?

The comparison purpose is front-loaded and the example is useful. The description is somewhat long and repeats output-field details that an output schema may already cover, but it remains focused and readable.

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?

For a 7-parameter comparison tool with full schema coverage, annotations, and an output schema, the description provides enough context: what is compared, how hospitals are identified, what price fields appear, and how missing prices are represented.

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 the schema already fully documents all seven parameters, including CCN format, code examples, enums, and code_type inference. The description reinforces that ccns are CCNs from the price-search tools and gives an MS-DRG example, but adds little parameter semantics 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 description states a specific comparison verb and resource: side-by-side prices for one service at up to 10 named hospitals by CCN. It clearly distinguishes this from hospital_price_search and hospital_price_coverage by emphasizing comparison across named hospitals.

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 a concrete usage example and tells the agent that CCNs come from hospital_price_search or hospital_price_coverage. It does not explicitly state when not to use it or route single-hospital price lookups to search, but the intended context is clear.

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.