MedPrice AI

Get hospital chargemaster cost

get_hospital_chargemaster_cost

Read-only

Lookup hospital chargemaster cost

Input Schema

TableJSON Schema

Name	Required	Description
`code`	Yes
`code_type`	Yes	Code system the chargemaster/billing code belongs to, e.g. APR-DRG, CDM, CPT, HCPCS, MS-DRG, RC. Hospitals may also support additional proprietary code types not listed here.
`hospital_id`	Yes	Opaque hospital identifier from list_hospitals.
`revision_id`	No	Optional. A revision_id from list_hospitals' per-hospital revisions array, to price that specific past revision instead of the hospital's latest one. Omit to use the latest revision.
`methodologies`	No	Pricing methodologies to price, one result per entry in request order. Omit or pass an empty array to get a single aggregate result across all methodologies.

Output Schema

TableJSON Schema

Name	Required	Description
`found`	No	True if at least one entry in results was found.
`results`	No	One entry per requested methodology, in request order - or, when the methodologies filter was left empty, exactly one aggregate entry.
`hospital`	No	Hospital name returned by the MedPrice AI backend.
`hospital_id`	No	Opaque hospital identifier to use with get_hospital_chargemaster_cost or list_hospitals.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 26, 2026

addedOutput schema / properties / results / items / properties / cost / properties / sample_count_exact

Added value: +{
+  "description": "True iff sample_count_sum_min == sample_count_sum_max, i.e. no contributing row was a de-identified '1 through 10' range.",
+  "type": "boolean"
+}

addedOutput schema / properties / results / items / properties / cost / properties / sample_count_sum_max

Added value: +{
+  "description": "Upper bound on the summed CMS sample-remittance count across contributing payer rows. Equal to sample_count_sum_min unless a de-identified '1 through 10' row narrowed it to a range.",
+  "type": "integer"
+}

addedOutput schema / properties / results / items / properties / cost / properties / sample_count_sum_min

Added value: +{
+  "description": "Lower bound on the summed CMS sample-remittance count across contributing payer rows. Equal to sample_count_sum_max unless a de-identified '1 through 10' row narrowed it to a range.",
+  "type": "integer"
+}

Changed7 schema fields changedSep 18, 2026

addedInput schema / properties / methodologies

Added value: +{
+  "description": "Pricing methodologies to price, one result per entry in request order. Omit or pass an empty array to get a single aggregate result across all methodologies.",
+  "items": {
+    "enum": [
+      "case rate",
+      "fee schedule",
+      "other",
+      "percent of total billed charges",
+      "per diem"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / methodology

Removed value: -{
-  "description": "Pricing methodology. Omit to aggregate across all methodologies.",
-  "enum": [
-    "case rate",
-    "fee schedule",
-    "other",
-    "percent of total billed charges",
-    "per diem"
-  ],
-  "type": "string"
-}

removedOutput schema / properties / cost

Removed value: -{
-  "properties": {
-    "avg": {
-      "type": "string"
-    },
-    "code": {
-      "type": "string"
-    },
-    "code_type": {
-      "type": "string"
-    },
-    "max": {
-      "type": "string"
-    },
-    "median": {
-      "type": "string"
-    },
-    "min": {
-      "type": "string"
-    },
-    "std_dev": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / description

Removed value: -{
-  "properties": {
-    "code_description": {
-      "type": "string"
-    },
-    "hospital_name": {
-      "type": "string"
-    },
-    "location": {
-      "type": "string"
-    },
-    "methodology_note": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

changedOutput schema / properties / found / description

Previous value: -"Whether a matching chargemaster cost record was found."New value: +"True if at least one entry in results was found."

addedOutput schema / properties / hospital_id

Added value: +{
+  "description": "Opaque hospital identifier to use with get_hospital_chargemaster_cost or list_hospitals.",
+  "type": "string"
+}

addedOutput schema / properties / results

Added value: +{
+  "description": "One entry per requested methodology, in request order - or, when the methodologies filter was left empty, exactly one aggregate entry.",
+  "items": {
+    "properties": {
+      "cost": {
+        "properties": {
+          "avg": {
+            "type": "string"
+          },
+          "code": {
+            "type": "string"
+          },
+          "code_type": {
+            "type": "string"
+          },
+          "max": {
+            "type": "string"
+          },
+          "median": {
+            "type": "string"
+          },
+          "min": {
+            "type": "string"
+          },
+          "std_dev": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "description": {
+        "properties": {
+          "code_description": {
+            "type": "string"
+          },
+          "hospital_name": {
+            "type": "string"
+          },
+          "location": {
+            "type": "string"
+          },
+          "methodology_note": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "found": {
+        "description": "Whether a matching chargemaster cost record was found for this methodology.",
+        "type": "boolean"
+      },
+      "methodology": {
+        "description": "Methodology this entry is scoped to. Empty when aggregated across all methodologies (the request's methodology filter was left empty).",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedAug 13, 2026

addedInput schema / properties / revision_id

Added value: +{
+  "description": "Optional. A revision_id from list_hospitals' per-hospital revisions array, to price that specific past revision instead of the hospital's latest one. Omit to use the latest revision.",
+  "type": "string"
+}

Changed1 schema field changedJul 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cost": {
+      "properties": {
+        "avg": {
+          "type": "string"
+        },
+        "code": {
+          "type": "string"
+        },
+        "code_type": {
+          "type": "string"
+        },
+        "max": {
+          "type": "string"
+        },
+        "median": {
+          "type": "string"
+        },
+        "min": {
+          "type": "string"
+        },
+        "std_dev": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "description": {
+      "properties": {
+        "code_description": {
+          "type": "string"
+        },
+        "hospital_name": {
+          "type": "string"
+        },
+        "location": {
+          "type": "string"
+        },
+        "methodology_note": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "found": {
+      "description": "Whether a matching chargemaster cost record was found.",
+      "type": "boolean"
+    },
+    "hospital": {
+      "description": "Hospital name returned by the MedPrice AI backend.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedJun 30, 2026

addedInput schema / properties / hospital_id

Added value: +{
+  "description": "Opaque hospital identifier from list_hospitals.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "code_type",
-  "code"
-]New value: +[
+  "hospital_id",
+  "code_type",
+  "code"
+]

AddedJun 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context such as how revision_id or methodologies affect the result, or what an aggregate result means. It simply restates the lookup nature without going beyond the annotations, so it provides no extra value in this dimension.

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?

The description is a single, front-loaded phrase with no filler words. It is concise and to the point, though it errs on the side of being too minimal. It earns its place but leaves room for more useful content without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters, an output schema, and sibling tools. The description provides only a one-line overview, which is minimally sufficient given the detailed schema and output schema. However, it does not explain how to use the tool relative to siblings, the behavior of methodologies, or what the returned cost represents. Clear gaps remain, so it is adequate but not complete.

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 80% (4 of 5 parameters have descriptions), so the baseline is 3. The description itself does not add any parameter-level meaning; it does not mention code_type, hospital_id, revision_id, or methodologies. The schema already carries the parameter semantics, and the description does not compensate for the undocumented 'code' parameter.

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 states a clear verb ('lookup') and resource ('hospital chargemaster cost'). It is not a tautology, but it does not explicitly differentiate from the sibling tool list_hospital_code_costs, which likely also deals with hospital costs. The verb 'lookup' suggests a single lookup rather than a list, but this is not spelled out.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus the sibling tools. There is no mention of alternatives, prerequisites, or contextual scenarios such as 'use this to get a specific price vs list_hospital_code_costs to enumerate prices'. The agent is left to infer usage from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MedPrice AI 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.