Skip to main content
Glama

Hospital price-transparency machine-readable file index

Find a hospital's price-transparency machine-readable file

resolve_hospital_mrf
Read-only

Where is this hospital's CMS standard-charges machine-readable file? Give a hospital name or part of one ("Prisma Health Richland", "Pennsylvania Hospital", "Abbott Northwestern") and get the file URL, the hospital's public price-transparency page, the health-system domain whose cms-hpt.txt declared it, and the verbatim line it was read from. Punctuation and case are ignored when matching. Hospital names are not unique — 64 names in this register belong to more than one hospital — so this returns a list and the domain tells them apart. Use list_hospitals_on_domain when you know the system rather than the hospital.

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": {
      "name": "<name>"
    },
    "name": "resolve_hospital_mrf"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHospital name or part of one. Case- and punctuation-insensitive; exact matches are returned first, then names starting with it, then names containing it.
limitNoHow many to return, 1–20. Default 20.
domainNoOptional health-system domain to narrow by, e.g. "mercy.net" or "https://www.mercy.net". Use it when a name matched more than one hospital.

Output Schema

NameRequiredDescriptionDefault
nameYes
noteNo
registerNo
hospitalsYes
hospitals_matchedYes
hospitals_returnedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real value by disclosing that results come back as a list, that 64 names are non-unique, and that the domain field disambiguates. It also states what each result contains (file URL, transparency page, declaring domain, verbatim source line), though the output schema likely covers the return shape.

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?

Front-loaded with the core question, then examples, then return contents, then the disambiguation caveat, then the sibling routing. Dense but every sentence carries information; no filler.

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

Completeness5/5

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

With annotations, a fully documented 3-parameter schema, and an output schema, the description supplies exactly the missing behavioral context: result multiplicity, name ambiguity, and sibling routing. Nothing an agent needs to call it correctly is absent.

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 100%, so the baseline is 3, but the description adds matching semantics (case and punctuation ignored) and the rationale for the domain parameter that the schema only hints at. The limit parameter is left to the schema, which is acceptable given full coverage.

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?

Opens with a specific question naming the exact resource (CMS standard-charges machine-readable file) and states the verb-like action (resolve by name). It is clearly distinguishable from list_hospitals_on_domain, which is named as the alternative for system-based lookup.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this when you have a hospital name, use list_hospitals_on_domain when you know the system instead. It also explains when to add the domain parameter (when a name matched more than one hospital), covering the main ambiguity case.

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