Skip to main content
Glama

get_cms_facility_benchmark

Read-only

Use when benchmarking hospital operating costs against CMS peer cohort or preparing a healthcare CFO board presentation. Returns peer_group context, benchmark_percentiles, metadata, source attribution, and optional database_row detail from the matched CMS benchmark row by bed size, state, and hospital type. Example: 300-bed acute care hospital in Illinois — peer group and percentile outputs show where operating metrics sit versus cohort benchmarks. Source: CMS HCRIS cost reports. $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": {
      "bed_size": "<bed_size>",
      "state": "<state>"
    },
    "name": "get_cms_facility_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
bed_sizeYes
hospital_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the return surface (peer_group, benchmark_percentiles, metadata, source attribution, database_row) and a per-call price of $0.02 USDC. It does not say what happens when no benchmark row matches or how large the returned percentiles set is.

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 'Use when...' trigger is front-loaded, followed by return fields, a worked example, source, and price — a logical order with no filler sentences. The example is somewhat redundant with the preceding sentence and could be trimmed, but it earns its place by illustrating the match keys.

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 correctly enumerates return fields and adds source and cost, which is the right division of labor. The main gap is input-side: no format guidance for the two required parameters, so an agent could still misfire on state or bed_size formatting despite the otherwise complete picture.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the burden, and it partially does: it names all three matching keys (bed size, state, hospital type). It does not specify formats or accepted values — state abbreviation vs full name, bed_size units, or valid hospital_type strings — leaving real ambiguity for an agent constructing the call.

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 clearly states a specific verb+resource: benchmarking hospital operating costs against CMS peer cohorts, with HCRIS cost reports as the source. That domain specificity distinguishes it from generic benchmark siblings like get_asc_benchmark or get_commodity_benchmark. It stops short of naming an explicit sibling alternative, keeping it from a 5.

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 concrete triggering contexts: benchmarking operating costs against a CMS peer cohort and preparing a healthcare CFO board presentation. There is no explicit when-not guidance or named alternative for non-hospital benchmarks, which keeps it below a 5.

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