Loa Healthcare Pricing

Pricing Estimate

get_pricing_estimate

Read-onlyIdempotent

Quick cash-price ballpark for one or more CPT codes, using the median cash price across hospitals in the state (from zip_code) or nationally. priceRange is the typical range (25th to 75th percentile of hospitals). Codes without enough data return insufficient_data and are listed in missingCodes; the total is null unless every code has data. Never fill gaps with your own estimate. For insurer rates or hospital-specific prices, use get_market_pricing or get_hospital_pricing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`zip_code`	No	ZIP code used to pick the state (omit for national figures)
`procedure_codes`	Yes	CPT procedure codes to price (e.g. ["99213", "85025"])

Output Schema

TableJSON Schema

Name	Required	Description	Default
`state`	Yes
`zipCode`	Yes
`disclaimer`	Yes
`procedures`	Yes
`provenance`	Yes
`limitations`	Yes
`missingCodes`	Yes
`estimatedCost`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedSep 28, 2026

changedInput schema / properties / zip_code / description

Previous value: -"ZIP code for regional pricing (defaults to national average)"New value: +"ZIP code used to pick the state (omit for national figures)"

removedOutput schema / properties / containsHeuristicEstimates
```
Removed value: -{
-  "type": "boolean"
-}
```

addedOutput schema / properties / estimatedCost / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / estimatedCost / type
```
Removed value: -"number"
```

addedOutput schema / properties / limitations

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / missingCodes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / procedures / items / properties / estimatedCost / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / properties / procedures / items / properties / estimatedCost / type
```
Removed value: -"number"
```

addedOutput schema / properties / procedures / items / properties / hospital_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

removedOutput schema / properties / procedures / items / properties / priceRange / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / procedures / items / properties / priceRange / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "max": {
+        "type": "number"
+      },
+      "min": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "min",
+      "max"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / procedures / items / properties / priceRange / properties

Removed value: -{
-  "max": {
-    "type": "number"
-  },
-  "min": {
-    "type": "number"
-  }
-}

removedOutput schema / properties / procedures / items / properties / priceRange / required
```
Removed value: -[
-  "min",
-  "max"
-]
```
removedOutput schema / properties / procedures / items / properties / priceRange / type
```
Removed value: -"object"
```

changedOutput schema / properties / procedures / items / properties / pricingMethod / enum

Previous value: -[
-  "observed_market_median",
-  "heuristic_cpt_range"
-]New value: +[
+  "observed_market_median",
+  "insufficient_data"
+]

addedOutput schema / properties / procedures / items / properties / scope

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "state",
+        "national"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / procedures / items / required

Previous value: -[
-  "code",
-  "description",
-  "estimatedCost",
-  "priceRange",
-  "pricingMethod",
-  "data_points"
-]New value: +[
+  "code",
+  "description",
+  "estimatedCost",
+  "priceRange",
+  "pricingMethod",
+  "scope",
+  "data_points",
+  "hospital_count"
+]

addedOutput schema / properties / state

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / zipCode / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / zipCode / type
```
Removed value: -"string"
```

changedOutput schema / required

Previous value: -[
-  "estimatedCost",
-  "procedures",
-  "zipCode",
-  "containsHeuristicEstimates",
-  "provenance",
-  "disclaimer"
-]New value: +[
+  "estimatedCost",
+  "procedures",
+  "zipCode",
+  "state",
+  "missingCodes",
+  "limitations",
+  "provenance",
+  "disclaimer"
+]

First observedJul 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive behavior: priceRange is the 25th-75th percentile band, codes with thin data return insufficient_data, they surface in missingCodes, total is null unless all codes have data, and the agent must not invent an estimate. That is far more than the safety hints the annotations provide.

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?

Four sentences, each carrying distinct load: what it computes, what the output field means, how gaps are handled, and where to go for other price types. Front-loaded with the core purpose and tightly written with no filler.

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?

With an output schema present the description is not obliged to explain returns, yet it clarifies the tricky semantics (percentile range, missingCodes, null total) that an agent would otherwise have to infer. Nothing needed to call this tool correctly 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% and both parameters are already documented there, including the omit-for-national rule for zip_code. The description reinforces the state-from-zip semantics but adds no new format or constraint detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('cash-price ballpark for one or more CPT codes') plus the aggregation basis (median cash price across hospitals in-state or nationally), so the agent knows exactly what number it gets back. It explicitly names the sibling tools that serve different price types, making it distinguishable without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing: 'For insurer rates or hospital-specific prices, use get_market_pricing or get_hospital_pricing,' and the schema/description together explain when to omit zip_code for national figures. Both the when-to-use and the when-to-use-something-else conditions are covered.

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.