Loa Healthcare Pricing

Hospital Search

search_hospitals

Read-onlyIdempotent

Search Loa's hospital directory by name or location and return hospital IDs plus address details. Use the returned hospital_ids with get_hospital_pricing to fetch source-labeled Published MRF and reviewed overlay prices.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City name
`name`	No	Hospital name to search for
`limit`	No	Max results (default 20)
`state`	No	Two-letter state code or full state name, e.g. "CA" or "New York".
`zip_code`	No	ZIP code

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`total`	Yes
`hospitals`	Yes
`provenance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

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"
+]

First observedJul 27, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already disclose that the tool is read-only, idempotent, and non-destructive. The description adds search scope and output context but does not disclose behavioral details like matching semantics, ordering, or rate limits. Adequate given the annotations, but not rich.

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 sentence front-loads the action, resource, and output; the second sentence adds valuable chaining context. Every sentence earns its place.

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?

Between the fully documented parameters, the output schema, safety annotations, and the downstream chaining hint, the description is complete enough for an agent to select and invoke the tool correctly. Nothing critical 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?

All five parameters are fully documented in the input schema, so the schema carries the semantic weight. The description's phrase 'by name or location' summarizes the parameter categories but adds no detail beyond what the schema already provides.

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 names the exact operation and resource: searching Loa's hospital directory by name or location. It also states the output (hospital IDs plus address details), which clearly differentiates it from provider or entity searches.

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 a concrete downstream workflow: use returned hospital_ids with get_hospital_pricing. However, it does not explicitly say when not to use this tool or compare it to search_providers/search_entities, so it falls just short of full alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Loa Healthcare Pricing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.