Skip to main content
Glama

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond them by disclosing the data source (CMS Care Compare methodology) and a per-call price of $0.02 USDC, though it says nothing about result freshness, pagination, or whether the benchmark figures are static.

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 and return contents are front-loaded, which is good. However the example sentence is a long triple-clause run-on mixing a weighting fact, a program-duration claim, and a distribution stat, and the pricing/source tail reads like sales copy rather than invocation guidance.

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?

With no output schema, the description must describe returns, and it does so at a high level (domain weights, distribution benchmarks, improvement priorities). For a tool with three undocumented optional parameters, though, an agent cannot tell how inputs change the answer, which is a meaningful completeness gap.

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, so the description carries the full burden and drops it. It never explains what state or hospital_name select, nor that all three inputs are optional and that omitting them presumably yields national benchmarks. The example only incidentally implies current_star_rating is a 1-5 scale.

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 names a specific resource (CMS Hospital Star Rating) and states what comes back: domain weights, national distribution benchmarks, and improvement priorities. It doesn't distinguish itself from the sibling get_cms_facility_benchmark, so an agent must infer the boundary from the name alone.

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 an explicit trigger condition: 'Use when advising on CMS Hospital Star Rating strategy or benchmarking a hospital quality performance trajectory.' That is a clear context for invocation, but there is no when-not guidance and no named alternative for adjacent benchmarking needs.

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