Skip to main content
Glama

Server Details

Why Medicare Part D restricts a drug, and the exception and appeal path to challenge it

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2024-11-05
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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 tools
medicare_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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Unifies 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 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and retrieving Medicare coverage policies including National and Local Coverage Determinations, National Coverage Analyses, and recent CMS coverage changes.
      103 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources