hospital_price_coverage
Pack: hospital-prices · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/hospital_price_coverage for the schema, then POST the same URL with its arguments for the data.
Is a hospital (by CCN or name), a state, or the whole store covered by hospital price data, and why not if not.
Tool description as the model sees it
Whether this store holds a hospital’s prices and, if not, WHY. Look up one hospital by CCN or by name (partial match), or summarise a state, or (no arguments) the whole store, including which states are loaded (the store is loaded state by state, so a hospital in an unloaded state is simply absent). Every hospital in a loaded state has a status: ok (prices held), blocked (its website refuses our requests; we do not evade blocks), not_found (no machine-readable file found), invalid_pointer, soft_404, unsupported_version, too_large, parse_error, no_matching_codes, not_fetched. Use before trusting an empty hospital_price_search, or to answer “does this tool cover Mayo Clinic”.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
ccn | string | no | CMS Certification Number, e.g. “330101”. |
name | string | no | Hospital name or part of it, e.g. “Mayo Clinic”. Up to 25 matches are returned. |
state | string | no | Two-letter state code, e.g. “MN”: counts by status for that state. |
status | string | no | With state: list hospitals having this status (e.g. “blocked”). |
Example call
Arguments
{
"name": "Advocate Christ"
}
curl
curl -X POST https://gateway.pipeworx.io/hospital-prices/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"hospital_price_coverage","arguments":{"name":"Advocate Christ"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('hospital_price_coverage', {
"name": "Advocate Christ"
});
More examples
{}
Response shape
| Field | Type | Description |
|---|---|---|
found | boolean | Whether at least one priced result was found |
reason | string | Machine-readable reason when found is false |
message | string | Plain-language explanation of the reason |
hint | string | How to narrow or fix the request |
data_as_of | string | null | File last-updated date, or the store cycle |
source | string | Publisher and dataset |
licence_note | string | Reuse-licence caveat |
coverage | object | Which states and how many hospitals the store holds |
matches | number | Name matches |
hospital | object | One hospital’s coverage status |
hospitals | array | Hospitals with status |
by_status | object | Counts per status |
store_cycle | string | Store cycle date |
Full JSON Schema
{
"type": "object",
"additionalProperties": true,
"properties": {
"found": {
"type": "boolean",
"description": "Whether at least one priced result was found"
},
"reason": {
"type": "string",
"description": "Machine-readable reason when found is false"
},
"message": {
"type": "string",
"description": "Plain-language explanation of the reason"
},
"hint": {
"type": "string",
"description": "How to narrow or fix the request"
},
"data_as_of": {
"type": [
"string",
"null"
],
"description": "File last-updated date, or the store cycle"
},
"source": {
"type": "string",
"description": "Publisher and dataset"
},
"licence_note": {
"type": "string",
"description": "Reuse-licence caveat"
},
"coverage": {
"type": "object",
"description": "Which states and how many hospitals the store holds",
"additionalProperties": true
},
"matches": {
"type": "number",
"description": "Name matches"
},
"hospital": {
"type": "object",
"additionalProperties": true,
"description": "One hospital's coverage status"
},
"hospitals": {
"type": "array",
"description": "Hospitals with status",
"items": {
"type": "object",
"additionalProperties": true
}
},
"by_status": {
"type": "object",
"additionalProperties": true,
"description": "Counts per status"
},
"store_cycle": {
"type": "string",
"description": "Store cycle date"
}
}
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the hospital-prices pack
{
"mcpServers": {
"hospital-prices": {
"url": "https://gateway.pipeworx.io/hospital-prices/mcp"
}
}
}
See Getting Started for client-specific install steps.