Skip to main content
Glama

get_hospital_care_compare_quality

Read-only

Use when evaluating hospital quality for a referral network decision, acquisition target assessment, or competitive quality analysis. Returns CMS Hospital Compare scores — safety, readmissions, patient experience, mortality, and overall star rating by hospital. Example: Northwestern Memorial — 5-star overall, top decile on mortality and safety, HCAHPS 87th percentile — benchmark for quality-driven referral network design. Source: CMS Care Compare synced data. $0.02 USDC per call.

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": {
      "hospital_name": "<hospital_name>"
    },
    "name": "get_hospital_care_compare_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
hospital_nameYesHospital or facility name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description's added value is the data provenance ("CMS Care Compare synced data") and the per-call price of $0.02 USDC, both genuinely useful for an agent. Gaps remain on behavior the agent would care about: how hospital names are matched (fuzzy vs exact), what happens when a name is ambiguous or unmatched, geographic coverage, and data freshness.

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?

Usage triggers are front-loaded, followed by return contents, then provenance and pricing, which is a sensible order. The Northwestern Memorial example is somewhat promotional in tone but earns its space by illustrating the shape of the response in the absence of an output schema.

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 burden of describing returns, and the metric enumeration plus the sample record do that reasonably well for a one-parameter lookup. What's missing is narrow but real: no statement of US-only scope, no name-matching behavior, and no indication of what an unmatched hospital returns.

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% for the single parameter, so the baseline is 3. The worked example ("Northwestern Memorial") mildly signals the expected name format, but the description never states whether partial names, addresses, or CCN identifiers are accepted — the one semantic question that matters for a single free-text lookup key.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-plus-resource framing ("Returns CMS Hospital Compare scores") and enumerates the returned domains — safety, readmissions, patient experience, mortality, overall star rating. That is enough to separate it from the supply-chain and value-based-care siblings, though it never names those neighbors explicitly, so an agent must infer the boundary itself.

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 three concrete triggering scenarios (referral network design, acquisition target assessment, competitive quality analysis), which is real when-to-use guidance rather than implied usage. It stops short of exclusions — nothing tells the agent when to prefer a sibling benchmark tool or what to do if the decision needs cost or supply-chain data instead.

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