Skip to main content
Glama

CMS — US Dialysis Facility Search

cms.dialysis.search
Read-onlyIdempotent

Search 7 500+ Medicare-certified dialysis (ESRD — End-Stage Renal Disease) facilities across the US with CMS 5-star quality ratings. Filter by state, city, ZIP code, facility name, and non-profit status. Returns CMS Certification Number (CCN), facility name, address, phone, profit/non-profit status, chain ownership flag, and 5-star quality rating from CMS ESRD Quality Incentive Program (QIP). Dialysis is required 3× per week for ESRD patients — finding a conveniently located, high-quality facility is critical for quality of life. Covers all DaVita, Fresenius, US Renal Care, and independent clinic locations. No auth — US Centers for Medicare & Medicaid Services public domain, unlimited free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity or town name to filter dialysis facilities (partial match). Example: "Atlanta", "Denver".
nameNoPartial facility name to search (case-insensitive substring match). Example: "DaVita", "Fresenius", "Dialysis Center".
limitNoMaximum number of dialysis facilities to return (1–100, default 20).
stateNoTwo-letter US state abbreviation to filter dialysis facilities (e.g. CA, FL, TX).
offsetNoNumber of results to skip for pagination (default 0).
zip_codeNo5-digit US ZIP code to filter dialysis facilities.
nonprofit_onlyNoWhen true, filter to only non-profit dialysis facilities. Non-profit facilities may have different care incentives vs. for-profit chains.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety. The description adds value with 'No auth — US Centers for Medicare & Medicaid Services public domain, unlimited free,' and specifies coverage of DaVita, Fresenius, US Renal Care, and independent clinics. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and filters are front-loaded, but the sentence about dialysis frequency and quality of life adds contextual color that is not required for tool invocation. Still, the description is reasonably well-structured overall.

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?

The description covers scope, filter dimensions, returned data fields, coverage, and auth requirements. With an output schema present and schema descriptions covering all parameters, an agent has sufficient information to select and invoke the tool correctly.

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%, and the description merely restates the filter set (state, city, ZIP code, facility name, non-profit status) without adding semantics beyond the schema. Param details like partial matching and limits are already in the 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?

States a specific verb ('Search'), resource ('Medicare-certified dialysis facilities'), and scope ('across the US'), and enumerates return fields. The title and description clearly distinguish it from sibling CMS facility tools (hospital, nursing home, home health) by focusing on dialysis/ESRD.

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?

The description provides a clear use case (finding conveniently located, high-quality dialysis facilities) but does not explicitly name alternatives like cms.hospital.search or state when not to use this tool. Usage is implied by the domain-specific subject matter rather than explicit routing.

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.