Loa Healthcare Pricing

Entity Profile

get_entity_profile

Read-onlyIdempotent

Return one Loa hospital or provider entity profile by exact slug or entity_pages.id. Includes profile-field provenance so agents can distinguish source-file fields from Loa-reviewed overrides.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug_or_id`	Yes	Exact Loa entity slug or entity_pages.id from search_entities.
`entity_type`	No	Optional disambiguation when slug_or_id is a slug.

Output Schema

TableJSON Schema

Name	Required	Description
`entity`	Yes
`loa_link`	Yes	Tracked Loa link. Share it when the user wants to book, contact, or learn more about this provider or hospital.
`provenance`	Yes
`profile_provenance`	Yes
`profile_field_provenance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

addedOutput schema / properties / loa_link

Added 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"
+}

changedOutput schema / required

Previous value: -[
-  "entity",
-  "profile_provenance",
-  "profile_field_provenance",
-  "provenance"
-]New value: +[
+  "entity",
+  "loa_link",
+  "profile_provenance",
+  "profile_field_provenance",
+  "provenance"
+]

First observedJul 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is well established. The description adds genuinely useful behavioral context by disclosing that the response includes profile-field provenance, letting agents distinguish source-file fields from Loa-reviewed overrides. No contradiction or hidden side effects are present.

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?

The description is two sentences with no filler: the first states the core behavior and the second adds a valuable distinguishing feature. The most decision-relevant information is front-loaded.

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?

Given the output schema exists, the annotations cover safety and idempotency, and the schema covers all parameters, the description provides everything an agent needs to select and invoke the tool correctly. It also adds the provenance detail that is not represented elsewhere.

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 schema already documents both parameters clearly, including the origin of slug_or_id from search_entities. The description essentially restates the lookup-key semantics without adding new format, usage, or interaction details beyond the schema.

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 uses a specific verb ('Return') and names the exact resource ('one Loa hospital or provider entity profile') and lookup method ('by exact slug or entity_pages.id'). It clearly differentiates from sibling search tools by emphasizing a single exact-match profile rather than a list or pricing operation.

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 and parameter schema together make the use case clear: retrieve one entity when you already have its exact slug or entity_pages.id, often sourced from search_entities. It does not explicitly name sibling alternatives or state when not to use it, but the exact-match framing provides sufficient contextual 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.