Loa Healthcare Pricing

Entity Prices

get_entity_prices

Read-onlyIdempotent

Return source-labeled prices for a Loa hospital or provider entity slug using the shared resolver. Use search_entities first if the slug is unknown. Results include provenance and explicit unavailable rows for requested CPT codes with no current price.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Exact Loa entity slug from search_entities or a Loa SEO page.
`limit`	No	Maximum number of prices, default 50, max 100.
`cpt_codes`	No	Optional CPT codes to filter. If omitted, returns current indexed prices up to the limit.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`entity`	Yes
`prices`	Yes
`loa_link`	Yes
`provenance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

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

Previous value: -[
-  "entity",
-  "prices",
-  "total",
-  "provenance"
-]New value: +[
+  "entity",
+  "loa_link",
+  "prices",
+  "total",
+  "provenance"
+]

First observedJul 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish that the operation is read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: results are source-labeled, include provenance, and return explicit unavailable rows for requested CPT codes with no current price. This gives the agent realistic expectations about output behavior.

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?

Three sentences with no filler. The primary action is front-loaded, the prerequisite is stated immediately after, and the key behavioral guarantees are summarized in the final sentence. 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?

For a read-only entity-price lookup with a rich input schema, an output schema, and safety annotations, the description covers the essential workflow: what is returned, how to handle an unknown slug, and what to expect in results. Nothing critical is missing for an agent to invoke it correctly.

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%, so the schema already documents slug, limit, and cpt_codes. The description adds some behavioral nuance around 'requested CPT codes' and unavailable rows, but it does not materially extend parameter meaning beyond what the schema provides. 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?

The description clearly states the action ('Return source-labeled prices') and the target resource ('a Loa hospital or provider entity slug'). It distinguishes the tool from market-level or estimate tools by emphasizing entity-level, source-labeled prices, though it does not explicitly contrast with the similarly named get_hospital_pricing sibling.

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 explicit actionable guidance: 'Use search_entities first if the slug is unknown.' This tells the agent what to do when the required parameter may be unavailable. However, it does not discuss when to prefer this tool over alternatives like get_hospital_pricing or get_market_pricing.

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.