Skip to main content
Glama
Sign In

QuantCalc Retirement Engine

by app.quantcalc
OverviewDiscussionsAdmin

Traditional IRA deduction and Roth IRA limit at a modified AGI (2026; 2027 ranges projected)

ira_deduction_and_roth_limit
Read-only

Runs IRS Publication 590-A Worksheet 1-2 (the deductible part of a traditional IRA contribution when you or your spouse is covered by a plan at work) and Worksheet 2-2 (the reduced Roth IRA contribution limit) for 2026 or 2027 on a given modified AGI, line by line, with the age-50 catch-up, the compensation cap, the spousal IRA rule and the worksheets' rounding and minimum; returns the deductible and nondeductible parts of a traditional contribution, the Roth IRA limit and the Roth room left. The limits and ranges are the website's IRA and Roth income-limit pages' own figures (the 2027 limit and ranges are projections under the statutory indexing formula until the IRS publishes them, labelled as such). Not tax advice.

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": {
      "filing_status": "<filing_status>",
      "age": "<age>",
      "magi": "<magi>"
    },
    "name": "ira_deduction_and_roth_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesYour age on December 31 of the tax year (18-110): 50 or older adds the catch-up.
magiYesModified AGI: the income the worksheets run on.
wagesNoYour wages (W-2 box 1): your compensation, which caps the contribution. Default: the MAGI is taken as your compensation.
amountNoThe contribution for the year. Default: your full limit.
coveredNoYou are covered by a retirement plan at work (the W-2 'Retirement plan' box). Default false.
tax_yearNo2026 (default) or 2027. 2027: the limits and phase-out ranges are the 2027 pages' PROJECTIONS under each limit's statutory indexing formula (the IRS's 2027 retirement-plan limits notice is not out yet), labelled as such. Stated in the result.
spouse_wagesNoJoint return only: the spouse's wages. Default 0.
filing_statusYessingle, mfj, hoh, mfs (lived with the spouse at some time in the year) or mfs_apart (married filing separately, lived apart all year: treated as unmarried).
spouse_coveredNomfj or mfs: your spouse is covered by a plan at work. Default false.
contribution_typeNotraditional (default): the deductible and nondeductible parts of the contribution. roth: your Roth IRA limit at this MAGI.
spouse_ira_contributionsNoJoint return only: the spouse's own IRA contributions (the spousal IRA rule). Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / contribution_type / description
      Previous value: -"traditional (default): the deductible part and the tax it saves. roth: your Roth IRA limit at this MAGI."New value: +"traditional (default): the deductible and nondeductible parts of the contribution. roth: your Roth IRA limit at this MAGI."
    • changedInput schema / properties / magi / description
      Previous value: -"Modified AGI. With it the worksheets run without a licence. Without it the engine's AGI for the income given is used (licence needed)."New value: +"Modified AGI: the income the worksheets run on."
    • removedInput schema / properties / other_income
      Removed value: -{
-  "description": "Other taxable income (interest, other ordinary income). Default 0.",
-  "type": "number"
-}
    • removedInput schema / properties / spouse_age
      Removed value: -{
-  "description": "Joint return only: the spouse's age. Default: the same as age.",
-  "type": "integer"
-}
    • removedInput schema / properties / state
      Removed value: -{
-  "description": "Optional two-letter state of residence, or DC: adds the state tax saving (licence needed). Without it no state saving is figured.",
-  "type": "string"
-}
    • changedInput schema / properties / tax_year / description
      Previous value: -"2026 (default) or 2027. 2027: the limits and phase-out ranges are the 2027 pages' PROJECTIONS under each limit's statutory indexing formula (the IRS's 2027 retirement-plan limits notice is not out yet), labelled as such; the tax on the IRS's published 2027 amounts (Rev. Proc. 2026-35); the state line on each state's 2026 rules, labelled. Stated in the result."New value: +"2026 (default) or 2027. 2027: the limits and phase-out ranges are the 2027 pages' PROJECTIONS under each limit's statutory indexing formula (the IRS's 2027 retirement-plan limits notice is not out yet), labelled as such. Stated in the result."
    • changedInput schema / properties / wages / description
      Previous value: -"Your wages (W-2 box 1): your compensation. Default 0."New value: +"Your wages (W-2 box 1): your compensation, which caps the contribution. Default: the MAGI is taken as your compensation."
    • changedInput schema / required
      Previous value: -[
-  "filing_status",
-  "age"
-]New value: +[
+  "filing_status",
+  "age",
+  "magi"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / tax_year / description
      Previous value: -"2026 (default) or 2027. 2027 uses the 2027 pages' figures (projected until the IRS publishes them) and the engine's 2027 federal return (the IRS's published 2027 brackets, Rev. Proc. 2026-35); stated in the result."New value: +"2026 (default) or 2027. 2027: the limits and phase-out ranges are the 2027 pages' PROJECTIONS under each limit's statutory indexing formula (the IRS's 2027 retirement-plan limits notice is not out yet), labelled as such; the tax on the IRS's published 2027 amounts (Rev. Proc. 2026-35); the state line on each state's 2026 rules, labelled. Stated in the result."
  3. Changed1 schema field changed
    • changedInput schema / properties / tax_year / description
      Previous value: -"2026 (default) or 2027. 2027 uses the 2027 pages' figures (projected until the IRS publishes them) and the engine's projected federal return; stated in the result."New value: +"2026 (default) or 2027. 2027 uses the 2027 pages' figures (projected until the IRS publishes them) and the engine's 2027 federal return (the IRS's published 2027 brackets, Rev. Proc. 2026-35); stated in the result."
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real context beyond that: line-by-line worksheet execution, age-50 catch-up, compensation cap, spousal IRA rule, worksheet rounding/minimums, projection labeling, and a 'not tax advice' caveat. It does not describe error behavior or input validation limits.

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?

It is two dense sentences with the core operation front-loaded and the projection caveat and disclaimer placed after. The first sentence is long and run-on, but nearly every clause carries substantive information, so there is little waste.

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

Completeness5/5

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

For an 11-parameter, no-output-schema tool, the description states what is returned (deductible and nondeductible parts, Roth limit, Roth room left) and explains the 2027 projection caveat. Combined with the fully documented schema and read-only annotations, an agent has enough to invoke it correctly.

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 description coverage is 100%, so the schema already documents all 11 parameters thoroughly, making the baseline 3. The description reinforces meaning at the rule level (catch-up, compensation cap, spousal IRA rule) but adds little parameter-specific detail beyond what the schema fields already say.

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?

The description names specific IRS worksheets (590-A Worksheet 1-2 and Worksheet 2-2) and the exact outputs: deductible/nondeductible traditional parts, the Roth limit, and remaining Roth room. That is a clear verb-plus-resource statement, though it never names a sibling tool to distinguish itself from (e.g., the deduction comparison or projection tools).

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

Usage Guidelines4/5

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

It gives strong applicability context: use it when you or a spouse is covered by a workplace plan, for 2026 or projected 2027, with traditional or Roth contributions selected by contribution_type. It stops short of explicit when-not guidance or naming an alternative tool for adjacent questions.

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