MedPrice AI

List hospitals' provider charges for a code

list_code_provider_hospitals

Read-only

Each hospital's charges for a (code_type, code), one row per hospital and group of the group_by grouping (default: per billing class, methodology and setting; GROUP_BY_ALL gives one row per hospital), paginated. The billing-class-aware counterpart to list_hospital_code_costs, good for 'which hospital is cheapest for X'. Defaults/caps page_size at 500; includes total_count and hospital_count. Backed by the hospital-prices serving snapshot; fails with UNAVAILABLE until the server has opened one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code_type": "<code_type>",
      "code": "<code>"
    },
    "name": "list_code_provider_hospitals"
  }
}

Input Schema

Name	Required	Description
`code`	Yes
`query`	No	Optional case-insensitive hospital-name search.
`filter`	No	Keeps only some of the grouped rows (see group_by). Each field left out matches any value; set a field (even to its *_UNSPECIFIED value, which means 'not filed') to require it. Billing classes are never blended: a facility fee and a professional fee are separate bills.
`group_by`	No	Which rows exist: one per billing class + methodology + setting (GROUP_BY_PER_COMBINATION, the default), per billing class, per methodology, or GROUP_BY_ALL (one figure over everything, blending billing classes), or GROUP_BY_FACILITY_PLUS_PROFESSIONAL (one row per methodology and setting the hospital files under both the facility and the professional billing class, the two added together, i.e. the combined bill; terms are methodology and setting, no billing class; no row where there is no professional counterpart). Applied before filter, which may name only the terms the grouping still keeps (e.g. GROUP_BY_BILLING_CLASS with a methodology filter, or GROUP_BY_ALL with any filter, is rejected as INVALID_ARGUMENT).
`order_by`	No	Defaults to relevance when query is set, hospital id otherwise.
`code_type`	Yes	Code system the billing code belongs to, e.g. APR-DRG, CDM, CPT, HCPCS, MS-DRG, RC.
`page_size`	No
`page_token`	No	Opaque next_page_token from a previous response; only valid with the same request fields.
`min_sample_count`	No	Only rows backed by at least this many billing records (compared against the sample count's lower bound). Negative values are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / group_by / description

Previous value: -"Which rows exist: one per billing class + methodology + setting (GROUP_BY_PER_COMBINATION, the default), per billing class, per methodology, or GROUP_BY_ALL (one figure over everything, blending billing classes). Applied before filter, which may name only the terms the grouping still keeps (e.g. GROUP_BY_BILLING_CLASS with a methodology filter, or GROUP_BY_ALL with any filter, is rejected as INVALID_ARGUMENT)."New value: +"Which rows exist: one per billing class + methodology + setting (GROUP_BY_PER_COMBINATION, the default), per billing class, per methodology, or GROUP_BY_ALL (one figure over everything, blending billing classes), or GROUP_BY_FACILITY_PLUS_PROFESSIONAL (one row per methodology and setting the hospital files under both the facility and the professional billing class, the two added together, i.e. the combined bill; terms are methodology and setting, no billing class; no row where there is no professional counterpart). Applied before filter, which may name only the terms the grouping still keeps (e.g. GROUP_BY_BILLING_CLASS with a methodology filter, or GROUP_BY_ALL with any filter, is rejected as INVALID_ARGUMENT)."

changedInput schema / properties / group_by / enum

Previous value: -[
-  "GROUP_BY_PER_COMBINATION",
-  "GROUP_BY_BILLING_CLASS",
-  "GROUP_BY_METHODOLOGY",
-  "GROUP_BY_ALL"
-]New value: +[
+  "GROUP_BY_PER_COMBINATION",
+  "GROUP_BY_BILLING_CLASS",
+  "GROUP_BY_METHODOLOGY",
+  "GROUP_BY_ALL",
+  "GROUP_BY_FACILITY_PLUS_PROFESSIONAL"
+]

Changed3 schema fields changedNov 3, 2026

removedInput schema / properties / all_terms

Removed value: -{
-  "description": "One row per hospital, its figure over every billing class, methodology and setting. Cannot be combined with filter.",
-  "type": "boolean"
-}

changedInput schema / properties / filter / description

Previous value: -"Restricts which price terms are returned. Each field left out matches any value; set a field (even to its *_UNSPECIFIED value, which means 'not filed') to require it. Billing classes are never blended: a facility fee and a professional fee are separate bills."New value: +"Keeps only some of the grouped rows (see group_by). Each field left out matches any value; set a field (even to its *_UNSPECIFIED value, which means 'not filed') to require it. Billing classes are never blended: a facility fee and a professional fee are separate bills."

addedInput schema / properties / group_by

Added value: +{
+  "description": "Which rows exist: one per billing class + methodology + setting (GROUP_BY_PER_COMBINATION, the default), per billing class, per methodology, or GROUP_BY_ALL (one figure over everything, blending billing classes). Applied before filter, which may name only the terms the grouping still keeps (e.g. GROUP_BY_BILLING_CLASS with a methodology filter, or GROUP_BY_ALL with any filter, is rejected as INVALID_ARGUMENT).",
+  "enum": [
+    "GROUP_BY_PER_COMBINATION",
+    "GROUP_BY_BILLING_CLASS",
+    "GROUP_BY_METHODOLOGY",
+    "GROUP_BY_ALL"
+  ],
+  "type": "string"
+}

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive safety profile, but the description goes further: it discloses the default and 500-row cap on page_size, that responses carry total_count and hospital_count, and that the tool is backed by a serving snapshot and fails with UNAVAILABLE until one is opened. That error-mode disclosure is genuinely valuable and not derivable from the annotations.

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 content is front-loaded: row shape and default grouping come first, then the sibling routing, then pagination and failure behavior. It is dense but every clause carries information; only the trailing snapshot/UNAVAILABLE sentence could be trimmed slightly.

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 9-parameter tool with a nested filter object and no output schema, the description covers row granularity, grouping defaults, pagination caps, response summary fields, and an availability failure mode. Only the exact shape of the returned rows beyond the counts is left implicit.

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 78%, so the schema already documents most parameters, including the filter and group_by enums. The description adds meaning beyond it by stating the default grouping (per billing class, methodology and setting) and the effect of GROUP_BY_ALL, which clarifies intent for the highest-complexity parameter.

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 gives a specific verb and resource ('Each hospital's charges for a (code_type, code), one row per hospital') and explicitly names the sibling it complements ('the billing-class-aware counterpart to list_hospital_code_costs'). An agent can distinguish this from the other code-cost tools without opening a 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?

It supplies a concrete use case ('which hospital is cheapest for X') and positions itself relative to list_hospital_code_costs. It stops short of stating explicit when-not-to-use conditions or naming further alternatives among the many sibling tools, so it is clear but not exhaustive.

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.