Skip to main content
Glama

get_hospital_supply_chain_benchmark

Read-only

Use when benchmarking hospital supply chain efficiency against CMS peer cohort or building a materials management cost reduction case. Returns supply cost as percentage of operating expense at p25/p50/p75 by bed size and state. Example: 200-bed community hospital — supply cost 19.4% of operating expense vs 16.8% peer median — closing the gap to median recovers $2.6M annually at $130M operating budget. 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>"
    },
    "name": "get_hospital_supply_chain_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
bed_sizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/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 the safety profile is covered. The description adds genuinely new behavioral facts beyond that: the data source (CMS HCRIS cost reports) and the per-call price ($0.02 USDC), which matters for an agent deciding whether to call. It omits data vintage/lag and what happens when a cohort is too small, so it is not a 5.

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…' lead plus the metrics sentence is front-loaded and efficient. The worked example is long but earns its place by quantifying the recovery value ($2.6M on a $130M budget), making the tool's payoff concrete; the trailing source and price facts are one short clause each.

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?

For a read-only, two-parameter benchmark with no output schema, the description covers the return shape (three percentiles, two segmenting dimensions), the provenance, and the cost, which is enough to call it correctly. The notable remaining gap is the handling of the optional 'state' parameter and expected input format.

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 description coverage is 0%, so the description must carry parameter meaning and it only partly does. It explains that results are segmented by bed size and state and the worked example implies bed_size is a raw bed count (200-bed hospital), but it never specifies the state format (two-letter vs. full name), whether state is optional, or what the default cohort is when state is omitted.

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

Purpose5/5

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

The description states a specific verb and resource (benchmarking hospital supply chain efficiency) and defines the returned metric precisely: supply cost as a percentage of operating expense at p25/p50/p75 by bed size and state. That return-level specificity distinguishes it from the many other benchmark siblings (GPO contracts, category spend, CMS facility quality) without needing to open the schema.

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?

Two concrete use cases are given (CMS peer-cohort benchmarking, building a materials management cost reduction case), so an agent knows the intended context. It stops short of naming an alternative or stating when NOT to use it — e.g., no guidance pointing to get_gpo_contract_benchmark or spend-focused siblings — so it does not reach 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