part-d-cap
Medicare Part D out-of-pocket cap: when you hit it, and what the payment plan changes
Should I use this
Quality & Safety
Findings (1)
- LOWin medicare_part_d_out_of_pocket_cap
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"part-d-cap": {
"url": "https://insurewith.ai/mcp/part-d-cap"
}
}
}Remote endpoints
https://insurewith.ai/mcp/part-d-capstreamable-httpWhat it can do
Tool inventory
Tools (1)
⚪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.
Input 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"
]
}Community
Evidence