Skip to main content
Glama

Starfile

Check a nursing home

check_nursing_home
Read-onlyIdempotent

The inspection and penalty record of one U.S. nursing home from CMS data: star ratings, staffing, fines and payment denials, how many inspection citations it has (and how many at the actual-harm or immediate-jeopardy level), its most recent citations with dates, its chain and its owner organisations. Find it by CCN (6-character CMS number) or by name plus state or city. Returns other close matches when a name is ambiguous.

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": "check_nursing_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccnNoCMS Certification Number: 6 characters, the two-digit state code then four digits.
cityNoCity, to narrow a name match.
nameNoFacility name, e.g. "Pinecrest Example Care Center".
stateNoU.S. state as a two-letter code (NY) or full name (New York).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add context — and it does, disclosing the exact data returned (including severity levels of citations and recent citation dates) plus the ambiguity/fuzzy-match behavior on name lookups. With no output schema, this return-content disclosure is valuable; only the absence of auth or rate-limit notes keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: the first defines the returned data, the second the lookup keys, the third the ambiguity behavior. It is front-loaded with the highest-value information and contains no filler.

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

Completeness5/5

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

For a read-only single-record lookup with four optional parameters and no output schema, the description covers what data comes back, how to address the facility, and what happens on an ambiguous match. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so parameter meanings are already documented and the baseline is 3. The description adds modest value by framing the identifier combinations ('name plus state or city'), which clarifies how the optional parameters compose, but it introduces no format details beyond the schema.

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 — the inspection and penalty record of one U.S. nursing home from CMS data — and enumerates the contents (star ratings, staffing, fines, payment denials, citation counts at actual-harm/immediate-jeopardy level, recent citations, chain, owners). This makes it clearly distinguishable from a bulk sibling like search_nursing_homes without needing 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?

It gives concrete lookup paths ('by CCN ... or by name plus state or city') and notes that ambiguous names yield other close matches, which tells an agent how to invoke it and what to expect. It stops short of explicitly naming a search sibling as the alternative for discovery-style queries, so it falls just below a full 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