Skip to main content
Glama
Sign In

Loa Healthcare Pricing

by io.github.aanari
OverviewDiscussionsAdmin

Provider Search

search_providers
Read-onlyIdempotent

Find clinicians and healthcare organizations in the CMS NPI Registry by name, specialty, or location. Returns directory details, not prices.

Input Schema

NameRequiredDescriptionDefault
nameNoProvider name to search for (e.g. "John Smith")
limitNoMax results (default 20)
locationNoLocation to search in
specialtyNoMedical specialty (e.g. "Cardiology", "Family Medicine")

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
providersYes
provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
    • changedOutput schema / properties / providers / items / 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"
+  }
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / providers / items / 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"
+  }
+]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / providers / 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 / providers / items / required
      Previous value: -[
-  "npi",
-  "name",
-  "specialty",
-  "address",
-  "city",
-  "state",
-  "zip_code",
-  "phone"
-]New value: +[
+  "npi",
+  "name",
+  "specialty",
+  "address",
+  "city",
+  "state",
+  "zip_code",
+  "phone",
+  "loa_link"
+]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds useful context by naming the CMS NPI Registry as the data source and clarifying that results are directory details rather than prices. It does not discuss matching behavior or pagination, but the annotations and schema cover much of the operational profile.

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 tight sentences with no wasted language. The core purpose is front-loaded, followed immediately by a useful scope clarification about return content.

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?

Given the rich annotations, complete schema coverage, and presence of an output schema, the description supplies enough context for an agent to call the tool correctly. It could do slightly more to differentiate this search tool from sibling search tools, but no critical calling information is missing.

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 name, specialty, location, and limit. The description reinforces name, specialty, and location as search dimensions but does not add syntax or format details beyond the schema. This meets the baseline for a fully documented 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 uses a specific verb and resource: finding clinicians and healthcare organizations in the CMS NPI Registry. It also clarifies the return scope by saying it returns directory details, not prices. It does not explicitly distinguish itself from sibling search tools such as search_entities or search_hospitals, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates that the tool can search by name, specialty, or location and that it is not a pricing tool. However, it does not explicitly say when to use this tool instead of search_entities, search_hospitals, or the pricing-related siblings. Usage is implied rather than fully guided.

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