Skip to main content
Glama
Sign In

QuantCalc Retirement Engine

by app.quantcalc
OverviewDiscussionsAdmin

Medicare IRMAA tier for a MAGI

irmaa_check
Read-only

Returns the Medicare IRMAA tier a MAGI sets: the official 2026 tier (from 2024 MAGI) and the 2027 and 2028 tiers (from 2025 and 2026 MAGI) on the tables as QuantCalc projects them, labelled projected; with each the monthly Part B and Part D surcharge per person, the annual total for the people on Medicare, and the distance to the next tier. Reads the same CMS tables as the website's IRMAA calculator. Free: no licence needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "magi": "<magi>",
      "filing_status": "<filing_status>"
    },
    "name": "irmaa_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
magiYesModified AGI (AGI plus tax-exempt interest) of the 2024 return, which sets the 2026 premiums; also used for 2025 and 2026 unless they are given.
magi_2025No2025 MAGI, which sets the 2027 premiums. Default: magi.
magi_2026No2026 MAGI, which sets the 2028 premiums. Default: magi.
filing_statusYesFiling status: single, married filing jointly (mfj), married filing separately (mfs) or head of household (hoh).
cpi_assumption_percentNoThe CPI-U assumption of the projected 2028 floors and the 2027-2028 surcharge amounts: 2.0, 2.5 (default) or 3.0. The 2027 floors do not depend on it: they come from the published CPI-U, as on /irmaa-brackets-2027/.
both_spouses_on_medicareNoJoint return only: both spouses are on Medicare (the surcharge is per person). Default true, stated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / filing_status / description
      Previous value: -"2026 filing status: single, married filing jointly (mfj), married filing separately (mfs) or head of household (hoh)."New value: +"Filing status: single, married filing jointly (mfj), married filing separately (mfs) or head of household (hoh)."
  2. Changed1 schema field changed
    • changedInput schema / properties / cpi_assumption_percent / description
      Previous value: -"The CPI-U assumption of the projected 2027 and 2028 tables: 2.0, 2.5 (default) or 3.0. The 3.0 table's 2027 floors equal those /irmaa-brackets-2027/ computes from the published CPI-U."New value: +"The CPI-U assumption of the projected 2028 floors and the 2027-2028 surcharge amounts: 2.0, 2.5 (default) or 3.0. The 2027 floors do not depend on it: they come from the published CPI-U, as on /irmaa-brackets-2027/."
  3. Changed1 schema field changed
    • changedInput schema / properties / cpi_assumption_percent / description
      Previous value: -"The CPI-U assumption of the projected 2027 and 2028 tables: 2.0, 2.5 (the central case, default) or 3.0, the band /irmaa-brackets-2027/ prints."New value: +"The CPI-U assumption of the projected 2027 and 2028 tables: 2.0, 2.5 (default) or 3.0. The 3.0 table's 2027 floors equal those /irmaa-brackets-2027/ computes from the published CPI-U."
  4. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond them, notably that 2027/2028 figures are projections on QuantCalc's tables and are labelled as projected, that surcharges are per person, and that it is free with no licence. It does not discuss edge cases such as the lower MFS thresholds, which is the main remaining gap for a computation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core result and then the output breakdown; there is no filler. It is one dense run-on sentence, and phrases like 'on the tables as QuantCalc projects them, labelled projected' read awkwardly, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, full schema coverage and no output schema, the description correctly takes on the job of describing return values, which it does thoroughly. It is nearly complete; a note on how MFS or a single filer affects the per-person annual total would close the last gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the year-to-MAGI mapping, filing statuses, CPI options and both_spouses_on_medicare are already documented in the schema. The description reinforces the 2024/2025/2026 MAGI to 2026/2027/2028 tier linkage and the per-person nature of the surcharge implied by both_spouses_on_medicare, but adds little that the schema does not already carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns the Medicare IRMAA tier a MAGI sets') and then enumerates exactly what comes back: the official 2026 tier, projected 2027 and 2028 tiers, per-person Part B/Part D surcharges, annual total and distance to the next tier. An agent cannot confuse this with the tax-calculation siblings, though the description never names an alternative to differentiate against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the input contract (a MAGI plus filing status yields a tier), and the 'Free: no licence needed' note helps an agent decide it is safe to call. However, there is no explicit when-to-use vs. when-not guidance and no mention of prerequisites such as needing a 2024 return to anchor the 2026 tier.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QuantCalc Retirement Engine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources