Skip to main content
Glama

Hospital Search

search_hospitals
Read-onlyIdempotent

Find hospitals by name or location, with addresses, contact details, and IDs for get_hospital_pricing.

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
nameNoHospital name to search for
limitNoMax results (default 20)
stateNoTwo-letter state code or full state name, e.g. "CA" or "New York".
zip_codeNoZIP code

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
hospitalsYes
provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / hospitals / items / properties / loa_link / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "description": "Tracked Loa link. Share it when the user wants to book, contact, or learn more about this provider or hospital.",
      -    "properties": {
      -      "action": {
      -        "enum": [
      -          "book",
      -          "request",
      -          "website",
      -          "profile"
      -        ],
      -        "type": "string"
      -      },
      -      "label": {
      -        "type": "string"
      -      },
      -      "url": {
      -        "format": "uri",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "url",
      -      "action",
      -      "label"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "description": "Share this returned URL with its exact label. A website action redirects to the provider website; only a profile action opens a Loa listing. Do not infer the destination from the loacare.com domain.",
      +    "properties": {
      +      "action": {
      +        "enum": [
      +          "book",
      +          "request",
      +          "website",
      +          "profile"
      +        ],
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "Use this exact label as the link text; it identifies the destination.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "format": "uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url",
      +      "action",
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / provenance / properties / source_url / description
      Added value: +"Supporting source link. A CMS Hospital Price Transparency policy page is not the hospital source file; do not attribute hospital-published prices to CMS."
  2. Changed1 schema field changed
    • changedOutput schema / properties / hospitals / items / properties / loa_link / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "description": "Tracked Loa link. Share it when the user wants to book, contact, or learn more about this provider or hospital.",
      -    "properties": {
      -      "action": {
      -        "enum": [
      -          "book",
      -          "website",
      -          "profile"
      -        ],
      -        "type": "string"
      -      },
      -      "label": {
      -        "type": "string"
      -      },
      -      "url": {
      -        "format": "uri",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "url",
      -      "action",
      -      "label"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "description": "Tracked Loa link. Share it when the user wants to book, contact, or learn more about this provider or hospital.",
      +    "properties": {
      +      "action": {
      +        "enum": [
      +          "book",
      +          "request",
      +          "website",
      +          "profile"
      +        ],
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "format": "uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url",
      +      "action",
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / hospitals / items / properties / loa_link
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "description": "Tracked Loa link. Share it when the user wants to book, contact, or learn more about this provider or hospital.",
      +      "properties": {
      +        "action": {
      +          "enum": [
      +            "book",
      +            "website",
      +            "profile"
      +          ],
      +          "type": "string"
      +        },
      +        "label": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "format": "uri",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "url",
      +        "action",
      +        "label"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / properties / hospitals / items / required
      Previous value: -[
      -  "hospital_id",
      -  "name",
      -  "address",
      -  "city",
      -  "state",
      -  "zip_code",
      -  "phone",
      -  "website"
      -]New value: +[
      +  "hospital_id",
      +  "name",
      +  "address",
      +  "city",
      +  "state",
      +  "zip_code",
      +  "phone",
      +  "website",
      +  "loa_link"
      +]
  4. First observed

TDQS

A3.5/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, so the safety profile costs the description nothing. The description adds useful chaining context (returns IDs consumed by get_hospital_pricing) but says nothing about match semantics (exact vs fuzzy name matching) or how city/state/zip combine, which matters for a tool with all-optional filters.

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?

A single front-loaded sentence with no filler; the useful chaining hint to get_hospital_pricing is attached rather than buried. Nothing is repeated from the schema or annotations.

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 return-shape explanation is not owed, and annotations cover the safety profile. What is missing for correct invocation is whether filters are ANDed, whether an unfiltered call is valid, and when to use this versus search_entities — real gaps for a 5-parameter, no-required-parameter search.

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%, including a helpful note on the state parameter accepting either a code or a full name, so the schema carries the parameter burden. The description's 'by name or location' only loosely frames the filters and adds no combining or precedence guidance. Baseline 3 is appropriate.

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 (find hospitals) plus the lookup dimensions (name or location), which is enough for an agent to know what it returns. It does not distinguish itself from search_entities, the sibling most likely to overlap, though it does name get_hospital_pricing as the downstream consumer.

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: the mention of IDs 'for get_hospital_pricing' signals this is the discovery step before a pricing lookup. There is no explicit when-to-use or when-to-prefer-search_entities guidance, and no statement about what happens when zero filters are supplied.

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.