Skip to main content
Glama

SolvingHealth federal health data

search_hospitals

Search the CMS Hospital General Information file: ownership, type, emergency services, and overall star rating.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name
nameNoPartial facility name
limitNoMax results, 1-50
stateNoTwo-letter state code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does tell the agent the field families contained in the file. However, it says nothing about result ordering, whether matching is prefix/substring, what happens when no filters are supplied, or pagination behavior beyond the schema's limit. For an unfiltered-by-default search with no annotation coverage, these are meaningful gaps.

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 that names the dataset first and then the covered fields; no filler or repetition. It is arguably terse to the point of omitting useful behavior, but every word earns its place.

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?

For a simple four-parameter search with no output schema and no required arguments, the description is adequate to establish scope, and the schema covers the inputs. It stops short of explaining what a result record looks like structurally or how results are ordered/limited, which matters given there is no output schema to fall back on.

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% and all four parameters are self-documented with types, bounds and semantics (e.g. 'Two-letter state code', 1-50 limit). The description adds no parameter-level meaning beyond that, so the baseline of 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: search over the CMS Hospital General Information file, and enumerates the data domains it covers (ownership, type, emergency services, overall star rating). It is clear what the tool retrieves; it does not explicitly contrast itself with the sibling datasets, though the names differ enough that confusion is unlikely.

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 only implied by 'Search' plus the city/name/state parameters; there is no statement of when this dataset is the right one versus the other search_* tools, nor any exclusions or prerequisites. An agent can infer it is the hospital lookup, but the description does not do that work for it.

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.