Skip to main content
Glama

List the codes a hospital charges

list_hospital_provider_codes
Read-only

Lists the codes one hospital reports on its latest (or a given) revision, as list_codes does, each with that hospital's own all-terms sample counts. Paginated; supports query, sort and code_type like list_codes. 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>"
    },
    "name": "list_hospital_provider_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
queryNoOptional case-insensitive search over code prefix and descriptions.
code_typeNoCode system to list, e.g. CPT. Required unless query is set; with query it may be left empty to search across code types (CodeSummary.code_type tells the hits apart).
page_sizeNo
page_tokenNoOpaque next_page_token from a previous response; only valid with the same request fields.
hospital_idYesOpaque hospital identifier from list_hospitals.
revision_idNoOptional. A revision_id from list_hospitals. Omit for the latest revision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "CODE_SORT_UNSPECIFIED",
      -  "CODE_SORT_HOSPITAL_COUNT_DESC",
      -  "CODE_SORT_SAMPLE_COUNT_DESC",
      -  "CODE_SORT_CODE_DESC",
      -  "CODE_SORT_RELEVANCE"
      -]New value: +[
      +  "CODE_SORT_UNSPECIFIED",
      +  "CODE_SORT_HOSPITAL_COUNT_DESC",
      +  "CODE_SORT_SAMPLE_COUNT_DESC",
      +  "CODE_SORT_CODE_DESC",
      +  "CODE_SORT_RELEVANCE",
      +  "CODE_SORT_HOSPITAL_COUNT_ASC",
      +  "CODE_SORT_SAMPLE_COUNT_ASC",
      +  "CODE_SORT_MEDIAN_PRICE_DESC",
      +  "CODE_SORT_MEDIAN_PRICE_ASC",
      +  "CODE_SORT_PRICE_SPREAD_DESC"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / code_type / description
      Previous value: -"Optional code system to restrict to, e.g. CPT. Omit to list every code type."New value: +"Code system to list, e.g. CPT. Required unless query is set; with query it may be left empty to search across code types (CodeSummary.code_type tells the hits apart)."
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds value on top: it discloses pagination, the hospital-prices serving-snapshot backing, and a concrete failure mode (UNAVAILABLE until a snapshot is opened). It does not state default sort/order or response shape, but for a read-only list tool the operational context given is meaningful.

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 definition is two tight sentences with no filler, and the core scope statement is front-loaded before the pagination and snapshot caveats. The mid-sentence comparison 'as list_codes does' is slightly awkward phrasing but costs little space.

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 7-parameter, read-only list tool with no output schema, the description covers scope, pagination, filtering knobs, revision defaulting, and the snapshot prerequisite. Remaining gaps are minor: what 'all-terms sample counts' comprise and default sort ordering are not explained, but nothing blocks a correct call.

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 coverage is 71%, so most parameters are already documented in the schema (query, code_type, page_token, hospital_id, revision_id). The description only adds the indirect pointer that query/sort/code_type behave 'like list_codes' and that results are per-hospital sample counts; it does not clarify the enum values for sort or the default sort behavior, so it stays at the baseline for a well-covered schema.

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 ('Lists the codes one hospital reports') plus the revision scope ('latest (or a given) revision'), and distinguishes itself from the global sibling by explicitly comparing to list_codes. An agent can tell it apart from list_hospital_code_costs or get_hospital_provider_code_costs because the output unit is stated: each code with that hospital's own all-terms sample counts.

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?

Usage is conveyed only indirectly, by saying it behaves 'as list_codes does' and 'supports query, sort and code_type like list_codes'. There is no explicit statement of when to pick this over the many sibling cost/rate tools, though the snapshot prerequisite ('fails with UNAVAILABLE until the server has opened one') does tell the agent when the call will not work.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.