coverage-exception

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

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
100%
Qualität der Benennung
60%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Befunde (2)

  • LOWTool 'medicare_part_d_out_of_pocket_cap' name length outside 3-30 rangein medicare_part_d_out_of_pocket_cap
  • LOWTool 'medicare_coverage_restriction_and_exception' name length outside 3-30 rangein medicare_coverage_restriction_and_exception

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~458Tokens (Tool-Definitionen)
~1.2 KBTypische Antwortgröße
Minimale Auswirkung auf die Aufmerksamkeit (0.36% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "coverage-exception": {
      "url": "https://insurewith.ai/mcp"
    }
  }
}

Remote-Endpunkte

https://insurewith.ai/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (2)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
⚪medicare_part_d_out_of_pocket_cap(monthly, drug, deductible, join, year)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "monthly": {
      "type": "string",
      "description": "Expected monthly out-of-pocket spend on covered drugs, in USD, e.g. \"300\""
    },
    "drug": {
      "type": "string",
      "description": "Optional drug name — checks formulary status and whether spending on it counts toward the cap"
    },
    "deductible": {
      "type": "string",
      "description": "Optional plan drug deductible in USD, e.g. \"615\" or \"0\""
    },
    "join": {
      "type": "string",
      "description": "Optional month (1-12) the payment plan would be joined"
    },
    "year": {
      "type": "string",
      "description": "Optional plan year: 2026 or 2027"
    }
  },
  "required": [
    "monthly"
  ]
}
🟡medicare_coverage_restriction_and_exception(drug, state)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "drug": {
      "type": "string",
      "description": "Brand or generic drug name, e.g. \"Humira\", \"adalimumab\""
    },
    "state": {
      "type": "string",
      "description": "Optional 2-letter US state code, e.g. \"TX\""
    }
  },
  "required": [
    "drug"
  ]
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet2 Tools
verifiziertVersion nicht aufgezeichnet2 Tools