MedPrice AI

Batch get a hospital's provider charges

batch_get_hospital_provider_code_costs

Read-only

Batch counterpart to get_hospital_provider_code_costs: one hospital's provider charges for 1 to 100 codes in a single call, results in request order. A code the hospital doesn't charge is an entry with no costs, not an error. 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": {
      "hospital_id": "<hospital_id>",
      "codes": "<codes>"
    },
    "name": "batch_get_hospital_provider_code_costs"
  }
}

Input Schema

Name	Required	Description
`codes`	Yes
`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).
`hospital_id`	Yes	Opaque hospital identifier from list_hospitals.
`revision_id`	No	Optional. A revision_id from list_hospitals. Omit for the latest revision.

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"
+]

Changed2 schema fields changedNov 3, 2026

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.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses request-order results, that a non-charged code returns an entry with no costs rather than an error, and that the tool depends on a hospital-prices serving snapshot and fails with UNAVAILABLE until one is opened. These are meaningful operational behaviors that an agent could not infer from the read-only annotations alone.

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?

Three compact sentences, front-loaded with the batch purpose and followed by exception behavior and availability constraints. Every sentence contributes distinct information with no redundant restatement.

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 complex nested tool with no output schema, it covers the essential call behavior: batching limits, ordering, missing-code handling, and snapshot availability. It is slightly incomplete on what a returned provider-charge entry contains, but the most important operational caveats are present.

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 high at 80%, and the schema itself explains filter, group_by, hospital_id, and revision_id in detail. The description adds useful semantics beyond the schema by stating the 1-to-100 code limit in prose and guaranteeing results in request order, though it does not add meaning for code_type or the grouped-row parameters beyond what the schema already says.

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 states a specific verb and resource: batch-fetching one hospital's provider charges for 1 to 100 codes. It explicitly identifies itself as the batch counterpart to get_hospital_provider_code_costs, making the distinction from the singular sibling clear without opening either 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 names the singular sibling and establishes that this tool is for batching 1 to 100 codes in one call, which gives clear context for choosing it. It stops short of an explicit 'use the singular tool for one code' instruction, but the routing implication is strong.

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.