Loa Healthcare Pricing

Entity Search

search_entities

Read-onlyIdempotent

Search Loa runtime hospital and provider entity pages by name or state. Use this before get_entity_prices when the user names a hospital or provider but does not know the exact Loa slug.

Input Schema

TableJSON 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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context about querying by name/state and the slug prerequisite, but it does not disclose behaviors like partial matching, result ordering, or pagination beyond what the schema already provides.

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 concise sentences with no filler. The core search scope is front-loaded, followed by a clear usage recommendation. Every sentence earns its place.

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 schema, an output schema, and safety annotations, the description covers the essential invocation context: what is searched, by what fields, and when it should be used. The main gap is not mentioning the closely related sibling search_hospitals and search_providers, which could affect tool selection.

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%, so the input schema fully documents all four parameters. The description loosely maps to query, state, and entity_type via 'by name or state' and 'hospital and provider', but it does not add meaningful semantics beyond the schema.

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?

The description states a clear verb and resource: searching Loa runtime hospital and provider entity pages by name or state. It is clear about what the tool does, but it does not explicitly differentiate from sibling tools search_hospitals and search_providers, which cover overlapping scopes.

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?

The description gives a specific, actionable use case: use before get_entity_prices when the user knows a hospital or provider name but not the exact Loa slug. However, it does not mention when to prefer search_hospitals or search_providers over this combined search tool.

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.