Skip to main content
Glama

CMS — US Home Health Agency Search

cms.home_health.search
Read-onlyIdempotent

Search 12 300+ Medicare-certified home health agencies across the US providing skilled nursing, physical therapy, occupational therapy, and speech pathology services in patients' homes. Filter by state, city, ZIP code, agency name, and whether nursing care is offered. Returns CMS Certification Number (CCN), agency name, address, phone, ownership type, services offered (nursing, PT, OT), and CMS quality-of-patient-care star rating. Essential for patients transitioning from hospital to home, post-surgical recovery, or managing chronic conditions without nursing home admission. No auth — US Centers for Medicare & Medicaid Services public domain, unlimited free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity or town name to filter agencies (partial match). Example: "Houston", "Phoenix".
nameNoPartial agency name to search (case-insensitive substring match). Example: "Amedisys", "LHC Group", "Encompass".
limitNoMaximum number of agencies to return (1–100, default 20).
stateNoTwo-letter US state abbreviation to filter home health agencies (e.g. TX, CA, NY).
offsetNoNumber of results to skip for pagination (default 0).
zip_codeNo5-digit US ZIP code to filter home health agencies.
offers_nursingNoWhen true, filter to only agencies that offer skilled nursing care services. Skilled nursing covers wound care, injections, IV therapy, and post-surgery monitoring.

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.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds valuable context: no authentication required, public domain data, unlimited free access, and a list of returned fields. This gives the agent confidence in safety and usage constraints.

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 description is somewhat verbose, including use-case and benefit statements that are not strictly necessary for invocation. It front-loads the core action and returns, but the extra prose could be trimmed without losing essential guidance.

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?

Given an output schema exists (so return values are defined) and all parameters are documented in the schema, the description covers the essential non-schema information: auth requirements, data source, and typical use cases. No critical missing info for an agent to call it 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%, so the input schema already documents all parameters. The description merely restates the filter options (state, city, ZIP, name, nursing) without adding new details or usage nuances. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Search') and a specific resource ('Medicare-certified home health agencies'), and enumerates the service types covered. It does not explicitly distinguish itself from sibling CMS search tools like cms.hospital.search or cms.nursing_home.search, but the resource is unambiguous.

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?

Provides concrete use cases ('patients transitioning from hospital to home, post-surgical recovery, or managing chronic conditions without nursing home admission'), which indicates when this tool is relevant. Does not explicitly state exclusions or alternatives, but the context is clear enough for an agent to decide.

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.