Skip to main content
Glama
Sign In

Loa Healthcare Pricing

by io.github.aanari
OverviewDiscussionsAdmin

Entity Profile

get_entity_profile
Read-onlyIdempotent

Get a hospital or provider profile by exact Loa slug or ID, with field provenance. On request, offer correction_url for corrections plus optional affiliation verification, or claim_url for affiliation only. Both forms allow intake without an account; dashboard access requires verification. Use the exact loa_link.label.

Input Schema

NameRequiredDescriptionDefault
slug_or_idYesExact Loa entity slug or entity_pages.id from search_entities.
entity_typeNoOptional disambiguation when slug_or_id is a slug.

Output Schema

NameRequiredDescriptionDefault
entityYes
loa_linkYesShare 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.
provenanceYes
provider_actionsYes
profile_provenanceYes
profile_field_provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / properties / loa_link / description
      Previous value: -"Tracked Loa link. Share it when the user wants to book, contact, or learn more about this provider or hospital."New value: +"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."
    • addedOutput schema / properties / loa_link / properties / label / description
      Added value: +"Use this exact label as the link text; it identifies the destination."
    • 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."
    • addedOutput schema / properties / provider_actions
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "description": "Offer only when the user asks to correct, add prices to, or claim this listing.",
+      "properties": {
+        "claim_url": {
+          "description": "Request affiliation verification only. For corrections plus verification, use correction_url instead. Submitting does not grant dashboard access.",
+          "format": "uri",
+          "type": "string"
+        },
+        "correction_url": {
+          "description": "Suggest listing or price changes and optionally request affiliation verification in the same form. No separate claim or existing account is required.",
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "correction_url",
+        "claim_url"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "entity",
-  "loa_link",
-  "profile_provenance",
-  "profile_field_provenance",
-  "provenance"
-]New value: +[
+  "entity",
+  "loa_link",
+  "provider_actions",
+  "profile_provenance",
+  "profile_field_provenance",
+  "provenance"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / loa_link / properties / action / enum
      Previous value: -[
-  "book",
-  "website",
-  "profile"
-]New value: +[
+  "book",
+  "request",
+  "website",
+  "profile"
+]
  3. Changed2 schema fields changed
    • 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"
+]
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context: results carry field provenance, two correction paths exist, intake is anonymous while dashboard access requires verification. That account/auth nuance is exactly the kind of detail annotations cannot express, though the wording around 'on request' is vague about what triggers each URL.

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?

Purpose is front-loaded in the first sentence and no sentence is pure filler. The correction/claim sentence is dense and slightly tangled in construction, but it still carries actionable information about two distinct flows.

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 two-parameter read tool with an output schema and full annotation coverage, the description supplies everything needed to invoke it correctly: identifier exactness, what the response includes (provenance), and the follow-up correction paths. Missing only explicit routing guidance against the sibling search and pricing tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a real constraint beyond the schema: the identifier must be the exact loa_link.label, reinforcing the 'exact' semantics and warning against fuzzy or partial input. The entity_type disambiguation parameter is left to the schema, which is acceptable given full coverage.

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 specific verb and resource: fetch a hospital or provider profile by exact Loa slug or ID, including field provenance. The word 'exact' implicitly contrasts with the fuzzy lookup done by the search_* siblings, though no sibling is named in the description itself (only in the schema).

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 clear operating context: corrections use correction_url (with optional affiliation verification), affiliation-only uses claim_url, intake works without an account, and dashboard access requires verification. It does not explicitly rule out or route to alternatives like get_entity_prices or search_entities, so it falls short of full when/when-not 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 toolsInspect
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.

Resources