Skip to main content
Glama

Hospital price-transparency machine-readable file index

Check a claimed hospital file URL against the register

verify_quote
Read-only

Is this right? Check a claim about a hospital's price-transparency file — the machine-readable file URL, the public page, the domain — against the register instead of trusting it. Says whether the claim matches a stored value, appears only in the verbatim source quote, or differs (and then what the register says instead), and returns the source and quote so it can be traced upstream. Use it on a URL a model produced from memory: these URLs are long, they rot, and a plausible wrong one is indistinguishable from a right one until it is checked.

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": {
      "claimed_value": "<claimed_value>",
      "hospital": "<hospital>"
    },
    "name": "verify_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoWhich field the claim is about, if you know it. Without it, every stored field of the record is checked.
domainNoOptional health-system domain, needed when the name belongs to more than one hospital (64 names in this register do).
hospitalYesThe hospital name the claim is about, as resolve_hospital_mrf returns it.
claimed_valueYesThe value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29".

Output Schema

NameRequiredDescriptionDefault
matchNo
recordNo
verdictYesmatches_record: the claim equals a stored value (match.match_type says how exactly). matches_quote: it appears in the verbatim source quote but is not a stored value. differs: the record was found and says something else — stored_values shows what. not_found: the record was not located, which says nothing about whether the claim is true.
attestationYes
quote_sourceNo
claimed_valueYes
stored_valuesNo
in_source_quoteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world, so the bar is lower; the description still adds real behavioral content by disclosing the three outcome classes (match, quote-only, diff with the register's value) and that source and quote are returned for upstream tracing. It does not discuss partial matches or multi-field behavior, keeping it off a 5.

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?

Well front-loaded: the check, the outcome taxonomy, and the upstream-trace return value arrive in order. The opening rhetorical 'Is this right?' costs a few words before the verb lands, a small but real inefficiency.

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?

Output schema exists, annotations cover the safety profile, and the schema covers parameters, so the description's remaining job is motivation and outcome semantics — both supplied. An agent can decide when to call it and interpret the three-way result without further reading.

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 description coverage is 100%, so all four parameters — including the field/domain disambiguation logic and the 'as resolve_hospital_mrf returns it' constraint — are already documented. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource: check a claimed value about a hospital's price-transparency file (MRF URL, public page, domain) against the register. It also states the oppositional framing — 'instead of trusting it' — which separates it from resolution/lookup siblings without naming them.

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?

Gives a clear triggering condition: 'Use it on a URL a model produced from memory,' plus the rationale (long URLs, link rot, plausible-but-wrong). It does not name a sibling alternative or state an explicit when-not-use case, so it stops short of a 5.

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