Skip to main content
Glama

Get a hospital's public record

get_hospital
Read-onlyIdempotent

Gets one hospital's public record by CCN, or by name with a two-letter state. The record includes the address, CMS overall star rating, hospital type, owners from CMS ownership records, private equity flag, last ownership change, published outcome measures, and whether OpenHealth holds a current price file for the hospital.

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_hospital"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccnNoThe hospital's six-character CMS Certification Number (CCN), such as 360006.
nameNoThe hospital's name, such as Riverside Methodist Hospital. Use it with state when you have no CCN.
stateNoA two-letter US state code, such as OH. A hospital name needs this code.

Output Schema

NameRequiredDescriptionDefault
dataNo
notesNo
statusYes
sourcesNo
page_urlNo
release_idNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful content scope (ownership records, private equity flag, last ownership change, price-file availability), but is silent on what happens when a name matches multiple hospitals or on precedence when both ccn and name are supplied.

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?

A single front-loaded sentence leading with the verb and identification modes, with no filler. The trailing field list is long and largely duplicates what the output schema already specifies, which costs it a point.

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?

An output schema exists, so most of the field enumeration is redundant effort while genuine gaps remain. With zero required parameters, the description never explains what a call with no arguments does, nor how ambiguous name matches are resolved.

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 100%, so all three parameters are already documented with format examples and the name/state pairing rule. The description restates the pairing ("by name with a two-letter state") without adding format or precedence detail beyond the schema, so the baseline 3 applies.

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 ("Gets one hospital's public record") plus the two identification modes, and enumerates the record's contents. Differentiation from siblings is only implicit (the price-file flag hints that get_hospital_prices returns actual prices), but an agent can still tell what this tool returns versus a doctor or procedure lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the CCN-vs-name+state choice is described, but that guidance is already in the schema. There is no explicit when-to-use/when-not, no pointer to get_hospital_prices for actual prices, and no guidance on switching to search_providers when the hospital identity is unknown.

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