coverage-exception
Server Details
Why Medicare Part D restricts a drug, and the exception and appeal path to challenge it
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2024-11-05
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools address clearly distinct Medicare Part D topics: one handles coverage restrictions, exceptions, and appeals; the other projects out-of-pocket spending against the annual cap. There is no overlap or realistic chance of selecting the wrong tool.
Both tool names follow the same snake_case pattern with a medicare_ prefix and a descriptive noun phrase. Though the second tool inserts part_d as a topic modifier, the naming style is consistent and predictable.
Two tools is on the thin side for a Medicare Part D server, but each tool covers a substantial subdomain. The count is borderline rather than excessive or severely deficient.
The coverage exception tool covers the main coverage problems and appeal paths, and the out-of-pocket cap tool addresses a major related cost question. Plan-specific clinical criteria and appeal deadlines are explicitly unavailable, which is a notable but intentional limitation rather than an accidental gap.
Available Tools
2 toolsmedicare_coverage_restriction_and_exceptionAInspect
For a drug on Medicare Part D, name the coverage problem — covered, prior authorization, step therapy, quantity limit, or not on formulary — and give the exception and appeal path with the CMS-named levels of appeal, who must submit the request, and what to ask the plan and the prescriber. Returns per-plan flag counts across plans held. Plan-specific clinical criteria and appeal deadlines are NOT held and are never inferred; they are returned in an explicit "unavailable" block rather than guessed.
Inputs: drug (required), state.
medicare_part_d_out_of_pocket_capAInspect
Project month-by-month Medicare Part D out-of-pocket spending against the statutory annual cap, identify the month the cap is reached, quantify what the cap itself saves, and compare normal payment timing against the Medicare Prescription Payment Plan — which spreads the SAME total across the year without reducing it. Supports plan years 2026 and 2027 and fails closed to 2026 for any unsupported year rather than extrapolating. This is a standard-benefit simulation, NOT a plan-specific pharmacy quote: plan negotiated prices and plan cost sharing are not held and are never inferred.
Inputs: monthly (required), drug, join, year, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Medicare Part D out-of-pocket cap: when you hit it, and what the payment plan changes
Insurer denial rates, appeal outcomes, appeal rights, and drug denial playbooks.
CMS Medicare drug price negotiation: the Maximum Fair Price (MFP) for every drug CMS has selected…
US drug price benchmarks — what a pharmacy PAYS and what Medicare PAYS OUT.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides unified access to drug formulary data from US ACA marketplace health insurance plans, enabling drug search, coverage details, restriction info, and plan comparison across thousands of plans.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-integrated prescription review with incomplete laboratory evidence, using deterministic rules and language-model guardrails to enforce approval authority boundaries.MIT
- AlicenseNot gradedqualityCmaintenanceUnifies five public US-government drug datasets into a single sourced page per GLP-1/cardiometabolic drug, providing cost, shortage, label, and alternatives. The MCP server exposes the same Drug contract as the UI for agent-native access.71,500,813 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving Medicare coverage policies including National and Local Coverage Determinations, National Coverage Analyses, and recent CMS coverage changes.103 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.