Loa Healthcare Pricing

Entity Search

search_entities

Read-onlyIdempotent

Find Loa hospital and provider listings by name or state. Resolve the exact slug before profile, price, or source lookups.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results, default 20, max 50.
`query`	No	Hospital or provider name to search for.
`state`	No	Two-letter state code or full state name, e.g. CA or New York.
`entity_type`	No	Optional filter for hospital or provider entities.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedOutput schema / properties / entities / 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."

Changed1 schema field changedOct 14, 2026

changedOutput schema / properties / entities / 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"
+  }
+]

Changed2 schema fields changedSep 24, 2026

addedOutput schema / properties / entities / 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 / entities / items / required

Previous value: -[
-  "id",
-  "entity_type",
-  "slug",
-  "canonical_name",
-  "display_name",
-  "city",
-  "state",
-  "zip_code",
-  "data_quality_score",
-  "updated_at"
-]New value: +[
+  "id",
+  "entity_type",
+  "slug",
+  "canonical_name",
+  "display_name",
+  "city",
+  "state",
+  "zip_code",
+  "data_quality_score",
+  "updated_at",
+  "loa_link"
+]

First observedJul 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so safety is covered; the description earns credit for disclosing this tool's role as a prerequisite resolution step rather than a data-fetching endpoint. It doesn't discuss result volume or what happens on zero matches, which the limit parameter hints at but never explains.

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, no filler, and the primary action is front-loaded before the follow-up workflow instruction. Every clause contributes either capability or sequencing.

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 a full output schema, rich annotations, and complete parameter descriptions, the description only needs to place the tool in the workflow, which it does. The remaining gap is that it never explains its relationship to search_hospitals and search_providers, which an agent choosing among eleven siblings would want.

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%, with each of the four parameters already documented including the enum and the limit bounds, so the schema carries the parameter burden. The description only restates that searching is by name or state and adds no syntax, matching behavior, or default detail beyond it.

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 concrete verb-plus-resource: find hospital and provider listings, filtered by name or state. The 'Loa' qualifier is unexplained and it never distinguishes itself from the sibling search_hospitals or search_providers tools, so an agent cannot tell from this text alone why the generic search exists alongside the specific ones.

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?

Gives real pipeline guidance: it should be called to resolve the exact slug before profile, price, or source lookups, which maps directly onto get_entity_profile, get_entity_prices, and explain_price_sources. It lacks an explicit 'when not to use' or a pointer to the hospital/provider-specific searchers, so guidance is clear but not complete.

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.