Loa Healthcare Pricing

Entity Prices

get_entity_prices

Read-onlyIdempotent

U.S. care only, for users anywhere. For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices. Get source-labeled prices by Loa listing slug; use search_entities to resolve it first. Missing CPT prices return explicit unavailable rows.

Input 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

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 changedOct 29, 2026
- addedOutput schema / properties / prices / items / properties / comparableMrfPrice / properties / includes
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / prices / items / properties / includes
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 29, 2026

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

Changed2 schema fields changedOct 15, 2026

addedOutput schema / properties / prices / items / properties / comparableMrfPrice / properties / practiceConfirmation

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "confirmedAt": {
+      "type": "string"
+    },
+    "details": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "itemId": {
+      "type": "string"
+    },
+    "versionId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "versionId",
+    "itemId",
+    "confirmedAt",
+    "details"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / prices / items / properties / practiceConfirmation

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "confirmedAt": {
+      "type": "string"
+    },
+    "details": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "itemId": {
+      "type": "string"
+    },
+    "versionId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "versionId",
+    "itemId",
+    "confirmedAt",
+    "details"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 14, 2026

changedOutput schema / 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 / 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

A3.9/5.0

Behavior4/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 is covered; the description adds genuinely new behavioral context — source-labeled provenance, a U.S.-only data-coverage boundary, and the fact that missing CPTs come back as explicit unavailable rows rather than being omitted. It stops short of describing ordering or pagination semantics, but that is largely unnecessary given the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, no filler, with the geographic scope front-loaded before the mechanics. The telegraphic fragments ("U.S. care only, for users anywhere") require a second read but are dense in information rather than padded.

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?

For a 3-parameter read with an output schema and full annotation coverage, the description supplies what structured fields cannot: regional coverage limits, the slug-resolution prerequisite, and missing-price behavior. Pagination/limit interaction is left to the schema, which is acceptable.

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% and all three parameters (slug, limit, cpt_codes) are documented in the schema, so the baseline is 3. The description only reinforces that the slug is a Loa listing slug resolved via search_entities and that a CPT filter yields unavailable rows for misses; it adds no format or edge-case detail 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 gives a specific verb and resource ("Get source-labeled prices by Loa listing slug") and scopes the data to a single entity plus optional CPT filter, so it is not a tautology of the name/title. It does not distinguish itself from adjacent pricing siblings like get_hospital_pricing, compare_local_prices, or get_market_pricing, so an agent must infer that the slug-scoping is the differentiator.

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 carries an explicit negative rule: "U.S. care only... For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices," plus a prerequisite ("use search_entities to resolve it first"). It never routes between the several other pricing tools, so the exclusion is clear but alternatives are unaddressed.

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.