Skip to main content
Glama

Starfile

List nursing homes

search_nursing_homes
Read-onlyIdempotent

List Medicare and Medicaid certified nursing homes by name, city or state, highest CMS overall rating first, with each home's rating, beds, special-focus status and abuse flag. Use check_nursing_home for one home's full record.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNoMax results (default 10, max 25).
queryNoName or part of a name (optional).
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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: results are sorted by CMS overall rating descending and each row includes rating, beds, special-focus status and an abuse flag, which tells the agent what to expect from the call. It does not discuss truncation or pagination beyond the limit parameter.

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?

Two sentences with no filler: the first front-loads capability, sort order and returned fields, the second handles sibling routing. Every clause earns its place.

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 usefully enumerates returned fields and sort order, which is exactly what the agent needs. Remaining gaps are minor: filter combinability and behavior when all filter params are omitted.

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 75% and the description maps its filter vocabulary (name, city, state) onto the query/city/state params, which is useful. However, it adds no syntax or format detail beyond the schema, and the interaction between filters remains undocumented, so the schema still carries most of the load.

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?

Names a specific verb (List) and resource (Medicare/Medicaid certified nursing homes), states the filterable dimensions (name, city, state), the sort order (highest CMS overall rating first), and the returned fields (rating, beds, special-focus status, abuse flag). It also explicitly distinguishes itself from check_nursing_home, so an agent can separate the two without opening schemas.

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?

The description clearly routes detail lookups to check_nursing_home, giving one explicit alternative and the condition that selects it. It stops short of explaining how the filters interact (e.g., whether city and state can be combined, or what happens with zero filters), so usage is clear but not exhaustive.

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