coverage-exception
Why Medicare Part D restricts a drug, and the exception and appeal path to challenge it
使うべきか
品質と安全性
検出事項(2)
- LOWmedicare_part_d_out_of_pocket_cap 内
- LOWmedicare_coverage_restriction_and_exception 内
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"coverage-exception": {
"url": "https://insurewith.ai/mcp"
}
}
}リモートエンドポイント
https://insurewith.ai/mcpstreamable-httpできること
ツール一覧
ツール(2)
⚪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.
入力スキーマ
{
"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.
入力スキーマ
{
"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"
]
}コミュニティ
エビデンス