Skip to main content
Glama

Calculate IRS Form 8880 Saver's Credit (2025-2026) & SECURE 2.0 50% Treasury Saver's Match (2027+)

calculate_savers_credit_and_2027_match
Read-only

Use this tool whenever a user asks about the IRS Form 8880 Retirement Savings Contributions Credit (Saver's Credit under IRC Sec. 25B), the new 2027 SECURE 2.0 50% Federal Treasury Saver's Match direct deposit (IRC Sec. 6433), the Form 8880 Line 4 prior-distribution reduction rule, or how lowering AGI via pre-tax 401(k)/IRA deductions unlocks the credit/match.

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": {
      "grossIncome": "<grossIncome>",
      "yourContribution": "<yourContribution>"
    },
    "name": "calculate_savers_credit_and_2027_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoTaxpayer age (must be 18+ to qualify).
yearNoTax year (2025, 2026 for Form 8880, or 2027 for SECURE 2.0 50% Saver's Match).
filingNoFederal tax filing status.single
grossIncomeYesGross income in USD before pre-tax 401(k)/IRA deductions.
yourContributionYesTaxpayer's annual IRA or 401(k) contribution in USD (first $2,000 counts).
spouseContributionNoSpouse's annual IRA or 401(k) contribution in USD if Married Filing Jointly (first $2,000 counts).
preTax401kOrIraDeductionNoPre-tax 401(k), Solo 401(k), SEP, Traditional IRA, or HSA deductions reducing AGI in USD.
testingPeriodDistributionsNoRetirement distributions taken during the Form 8880 Line 4 testing period in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered and the bar is lower. The description contributes domain behavior by surfacing the Line 4 prior-distribution reduction and the AGI-unlock mechanic, telling the agent the calculation is stateful with respect to distributions and deductions. It says nothing about what is returned (credit rate tier, dollar amount, match amount) or about eligibility caveats like the 18+ age rule, which remains buried in the schema.

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?

A single front-loaded sentence with the trigger first and the specific statutes/forms enumerated after; no filler or repetition. It is dense but every clause names a distinct covered scenario, so little is wasted.

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

Completeness3/5

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

With eight parameters, two enums, and no output schema, the definition covers the input side adequately via the schema but leaves the return side entirely unspecified — an agent cannot tell whether it gets a credit amount, a rate tier, a match amount, or all three. Given read-only annotations and full schema coverage, a 3 is a fair minimum-viable rating rather than a serious deficiency.

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 eight parameters including enums and defaults; baseline is 3. The description adds modest framing by tying preTax401kOrIraDeduction to AGI reduction and testingPeriodDistributions to the Line 4 rule, but it does not add format, interaction, or precedence guidance beyond that.

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?

Names the exact artifacts it handles: Form 8880 / IRC Sec. 25B Saver's Credit, the 2027 SECURE 2.0 Sec. 6433 50% Treasury match, the Line 4 distribution reduction, and AGI-lowering via pre-tax contributions. That is enough to separate it from siblings like calculate_roth_conversion or calculate_rmd_and_tax_cliffs. It never states the output as a verb+resource ('calculates X for a given taxpayer'), so it reads as a topic list rather than a description of what the tool produces.

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?

Provides explicit trigger conditions ('use this tool whenever a user asks about...') covering four concrete topic areas, which is stronger than most calculators get. It stops short of naming alternatives or when-not-to-use conditions (e.g., non-retirement credits, or the AGI-simulation sibling simulate_form_1040_and_bracket_room).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources