Skip to main content
Glama

Hospital price-transparency machine-readable file index

List every hospital a health system's cms-hpt.txt declares

list_hospitals_on_domain
Read-only

Which hospitals does this health system publish prices for? Give a domain ("mercy.net", "www.adventhealth.com", or a URL on it) and get every location its root cms-hpt.txt names, each with its machine-readable file URL, its public page and the line it was read from. This is how the files are actually published — one cms-hpt.txt can declare eighty-six hospitals — so it is the right call when you know the system but not the exact location name. With no domain it lists the 73 domains this register covers, with a count for each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_hospitals_on_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many locations to return, 1–20. Default 20.
domainNoThe health system's domain. Scheme, "www." and any path are ignored, so "https://www.mercy.net/billing" and "mercy.net" are the same system. Omit it to list the domains covered.

Output Schema

NameRequiredDescriptionDefault
noteNo
domainNo
registerYes
hospitalsNo
domains_coveredNoReturned instead of hospitals when no domain was given.
locations_matchedNo
locations_returnedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe, closed-world read, and the description still adds real substance: what each result row carries (machine-readable file URL, public page, source line) and the scale of a single cms-hpt.txt (eighty-six hospitals). It omits what happens when a domain is not among the 73 covered or is unreachable, which is the main behavioral gap.

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?

Three sentences, front-loaded with the question it answers, then the payoff, then the no-domain fallback. The eighty-six-hospitals aside earns its place as justification for the tool's existence; nothing is padding.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile, so the description only needs to explain scoping and mode selection — which it does. The one hole is the unaddressed interaction between 'get every location' and the limit parameter's ceiling of 20, which could mislead an agent about completeness of results.

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 100%, so both parameters are already documented, and the description mostly restates the domain normalization ('scheme, "www." and any path are ignored') rather than extending it. The 'every location' framing also sits uneasily with the limit parameter's 1–20 cap, a tension the description never resolves.

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 names a concrete verb and resource ('List every hospital a health system's cms-hpt.txt declares') and opens with the user-facing question it answers. It also carves out a distinct niche versus a location-level lookup ('the right call when you know the system but not the exact location name'), so an agent can place it against resolve_hospital_mrf 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 gives an explicit selection condition ('when you know the system but not the exact location name') and documents the second mode of use ('With no domain it lists the 73 domains this register covers'). It stops short of naming a sibling or stating when not to use it, so it is clear context rather than a full routing rule.

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.

Resources