Skip to main content
Glama

Find hospitals and health centers

find_facilities
Read-onlyIdempotent

Find US hospitals and community health centers near a zip code, or in a city and state, with each one's financial assistance (charity care) income limits. Use it when a person asks whether they can get free or discounted care at a US hospital or health center, needs help with a hospital bill, or asks how to apply for hospital financial assistance. Use it first when the patient names a place, not a specific hospital, or to get the facility id the other tools need. Takes a zip code, or a city and state. Returns name, address, phone, ownership, distance, data tier, and income limits as a percent of the poverty level for each facility. It does not say whether a household is eligible; check_eligibility does.

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

Input Schema

NameRequiredDescriptionDefault
zipNoFive-digit zip code. Use this or city + state.
cityNoCity name. Use with state when there is no zip.
kindNohospital, health_center (community health centers with sliding fees), or any.any
limitNo
stateNoTwo-letter US state code, for example "MA".
radius_milesNoSearch radius around the zip, in miles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, so the description's added value is elsewhere: it enumerates the returned fields (name, address, phone, ownership, distance, data tier, income limits) despite the absence of an output schema, and explicitly warns it does not determine household eligibility. It omits any note on result truncation tied to the limit parameter, which keeps this 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.

Conciseness4/5

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

Front-loaded with purpose, then usage triggers, then inputs, then returns, then the boundary with the sibling — a logical agent-readable order with no filler. There is mild redundancy between the usage sentences ('use it when...' and 'use it first when...') that could be tightened into one.

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 six-parameter read tool with no output schema, the description covers both input modes, the shape of the result, the workflow role (source of the facility id), and the handoff to check_eligibility. Nothing an agent needs in order to call it correctly or interpret the result 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 description coverage is 83%, so the schema already explains zip, city, state, kind, limit, and radius_miles. The description only restates the zip-or-city+state input mode, which the schema itself already documents, and adds no format or interaction details beyond that. Baseline 3 is appropriate.

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?

Opens with a specific verb and resource: find US hospitals and community health centers, by zip code or city+state, including financial assistance income limits. It clearly distinguishes itself from the other tools by naming check_eligibility as the eligibility-checking counterpart, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit triggering conditions (patient asks about free/discounted care, needs bill help, asks how to apply) and an ordering rule: use it first when a place rather than a specific hospital is named, or to obtain the facility id other tools require. It also states the exclusion boundary — eligibility is not answered here, check_eligibility handles that.

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