Skip to main content
Glama

Stratalize Intelligence

Get Hospital Care Compare Quality

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream data source ('CMS Care Compare synced data') and a per-call cost of $0.02 USDC, which matters for an agent deciding whether to invoke. It does not state how hospital names are matched or what happens on a miss, leaving a behavioral gap.

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 usage trigger, then the return payload, then provenance and price — a sensible order with no wasted framing. The Northwestern Memorial illustration is longer than needed and reads partly as marketing, but it does usefully demonstrate the shape and granularity of a result.

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?

No output schema exists, so the description carries the burden of describing returns, and it does: five named measure domains plus an overall star rating, with a concrete worked example. Combined with source and pricing disclosure, an agent has everything needed to decide to call it and interpret the result.

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?

There is only one parameter and schema coverage is 100%, so the baseline of 3 applies. The description does not add meaning beyond 'Hospital or facility name' — nothing about fuzzy matching, name normalization, ambiguity resolution, or whether system/network names are accepted, which is the main practical risk for a name-keyed lookup.

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?

States a specific verb and resource ('Returns CMS Hospital Compare scores') and enumerates the exact measures returned: safety, readmissions, patient experience, mortality, overall star rating. It is clearly distinguishable from siblings like get_hospital_supply_chain_benchmark by naming quality domains, though it never explicitly contrasts itself with get_cms_facility_benchmark, the closest-sounding alternative.

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?

Opens with an explicit when-to-use clause covering three concrete scenarios: referral network decisions, acquisition target assessment, and competitive quality analysis. It gives no when-not-to-use guidance and names no alternative tool for adjacent needs, so the agent must infer boundaries on its own.

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