Skip to main content
Glama

Stratalize Intelligence

Get Cms Star Rating

get_cms_star_rating
Read-only

Use when advising on CMS Hospital Star Rating strategy or benchmarking a hospital quality performance trajectory. Returns domain weights, national distribution benchmarks, and improvement priorities. Example: Mortality domain weighted at 22% of overall star — hospitals moving 3 to 4 stars typically require 18-month mortality improvement program — 3-star hospitals represent 41% of the national distribution. Source: CMS Care Compare methodology. $0.02 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cms_star_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
hospital_nameNo
current_star_ratingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, non-destructive behavior, so the description only needs to add context. It does: it names the data source (CMS Care Compare methodology) and discloses a per-call cost of $0.02 USDC, which is operationally important and not present in structured fields. It does not say what happens when optional identifiers are omitted or how the response is shaped, leaving a gap on a tool with all-optional parameters.

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 usage condition is correctly front-loaded, and the source and pricing lines earn their place. The 'Example:' sentence is overloaded, however, packing a domain weight, an 18-month improvement claim, and a distribution statistic into em-dash fragments, which blurs the line between illustration and returned data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with no output schema, the description reasonably enumerates the return payload (weights, distribution, priorities) and cites its source. What an agent still cannot determine is how inputs combine (are all three optional filters, or is one required in practice?) and whether a call with no arguments returns national-level context only, which matters for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters (state, hospital_name, current_star_rating), so the description carries the full burden and does not meet it. The only implicit hint is the illustrative 'hospitals moving 3 to 4 stars,' which gestures at current_star_rating without explaining its role, and nothing explains whether state or hospital_name scope the benchmarks versus identify a single hospital.

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 conveys what the tool delivers (domain weights, national distribution benchmarks, improvement priorities) and frames it around CMS Hospital Star Rating work, so an agent can tell it is a star-rating benchmark tool. It never states the core operation in a single crisp verb+resource phrase like 'returns the CMS star rating profile for a hospital,' and it does not differentiate itself from the sibling get_cms_facility_benchmark, which sounds closely related.

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 opening 'Use when advising on CMS Hospital Star Rating strategy or benchmarking a hospital quality performance trajectory' gives a clear triggering context. It stops short of exclusions or naming an alternative for adjacent needs, so an agent facing a general facility benchmarking question has no routing signal.

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