Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_sepp_72t_solver

Calculates penalty-free early retirement distributions from IRAs or 401(k)s under IRS Section 72(t), comparing amortization, annuitization, and RMD methods.

Instructions

IRS Section 72(t) / Notice 2022-6 Early Retirement Distribution Solver: Calculates penalty-free Substantially Equal Periodic Payments (SEPP) from qualified retirement plans (Traditional IRA, 401k) prior to age 59½ under IRC Section 72(t)(2)(A)(iv).

APPLIED ASSUMPTIONS & GOVERNING RULES:

  • Life Expectancy Table: Uses IRS Single Life Expectancy Table pursuant to Treas. Reg. § 1.401(a)(9)-9 (actuarial divisor factor = 84 - attained age).

  • Rate Cap Enforcement: Enforces IRS Notice 2022-6 interest rate ceiling, which mandates that the interest rate used cannot exceed the greater of 5.0% or 120% of the federal mid-term Applicable Federal Rate (AFR) for either of the two months preceding the month distributions begin.

  • Payment Frequency: Evaluates statutory annual distribution amounts and provides statutory monthly equivalent allowances (annual ÷ 12). Payments must be taken at least annually and maintained for the statutory period: the longer of 5 full years or until the account owner attains age 59½.

  • Evaluates all three IRS-approved methods: (1) Fixed Amortization, (2) Fixed Annuitization, and (3) Minimum Distribution (RMD).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke to determine penalty-free early retirement withdrawal schedules from qualified plans before age 59½ and compare fixed vs variable distribution options.

  • WHEN NOT TO USE: Do not use for Roth IRA basis distributions (which are already penalty- and tax-free) or non-qualified annuity contracts.

  • SIBLING ROUTING: Use omni_sepp_72t_solver for IRS 72(t) early retirement distributions. For standard retirement nest egg drawdown, see omni_retirement_nest_egg. For general finance queries, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic actuarial finance computation.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: ira_balance > 0, age between 18 and 80, interest_rate_pct between 0.1 and 10.0.

RETURNS:

  • Structured JSON object containing:

    • source (string): Canonical documentation URL

    • governing_guideline (string): "IRS Notice 2022-6 & IRC Section 72(t)(2)(A)(iv)"

    • inputs (object): Echoed input values { ira_balance, age, interest_rate_pct }

    • annual_distributions (object): Annual withdrawal amount in USD for each IRS method:

      • fixed_amortization (number): Level annual payment using amortization method ($/year)

      • fixed_annuitization (number): Level annual payment using annuity factor ($/year)

      • minimum_rmd (number): Year 1 payment using Required Minimum Distribution method ($/year)

    • monthly_allowances (object): Monthly installment equivalents (annual ÷ 12):

      • fixed_amortization (number): Monthly amortization installment ($/month)

      • fixed_annuitization (number): Monthly annuitization installment ($/month)

      • minimum_rmd (number): Monthly RMD installment ($/month)

    • advisory_note (string): IRS compliance advisory covering statutory 5-year/age 59½ term and one-time switch to RMD

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": {
      "ira_balance": "<ira_balance>",
      "age": "<age>"
    },
    "name": "omni_sepp_72t_solver"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesAccount owner's attained chronological age in years at distribution start (integer 18-80).
ira_balanceYesCurrent total qualified account balance in USD ($). Minimum $1,000.
interest_rate_pctNoSelected annual interest rate percentage (e.g. 5.0 for 5.0%). Enforced pursuant to IRS Notice 2022-6 ceiling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.2
    • changedInput schema / properties / age / description
      Previous value: -"Account owner's attained age"New value: +"Account owner's attained chronological age in years at distribution start (integer 18-80)."
    • changedInput schema / properties / interest_rate_pct / description
      Previous value: -"Selected interest rate (up to 5% or 120% AFR)"New value: +"Selected annual interest rate percentage (e.g. 5.0 for 5.0%). Enforced pursuant to IRS Notice 2022-6 ceiling."
    • addedInput schema / properties / interest_rate_pct / maximum
      Added value: +10
    • addedInput schema / properties / interest_rate_pct / minimum
      Added value: +0.1
    • changedInput schema / properties / ira_balance / description
      Previous value: -"Current account balance ($)"New value: +"Current total qualified account balance in USD ($). Minimum $1,000."
    • addedInput schema / properties / ira_balance / minimum
      Added value: +1000
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and meets it: it declares the tool read-only, idempotent, stateless, and deterministic with zero side effects. It also discloses validation bounds, the governing rate-cap rule, and the statutory 5-year/age-59½ maintenance requirement — behavior an agent could not infer from the schema alone.

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?

The text is front-loaded with purpose and organized under labeled sections (assumptions, usage, behavior, returns), which makes it scannable despite its length. There is mild redundancy between 'Pure deterministic actuarial finance computation' and 'read-only, idempotent, and stateless,' and the returns block is long, but the length is largely earned by the domain complexity and the absence of an output schema.

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?

No output schema exists, so the detailed RETURNS breakdown naming each method's annual and monthly fields is necessary rather than padding. Combined with the governing rules, validation bounds, and compliance advisory note, an agent has everything needed to invoke the tool and interpret its response.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning on top by explaining that interest_rate_pct is bounded by the Notice 2022-6 ceiling (greater of 5.0% or 120% of the mid-term AFR) and that age refers to attained age at distribution start. It does not add per-parameter defaults or units beyond what the schema already carries, keeping it short of a 5.

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

Purpose5/5

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

The description states a specific verb and resource — calculating SEpp distributions under IRC Section 72(t)(2)(A)(iv) — and immediately scopes it to pre-59½ withdrawals from qualified plans. It further enumerates the three IRS-approved methods (amortization, annuitization, RMD), so an agent knows exactly what computation is performed without opening the schema.

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 provides an explicit WHEN TO USE line, an explicit WHEN NOT TO USE line excluding Roth basis distributions and non-qualified annuities, plus sibling routing to omni_retirement_nest_egg and omni_universal_query. The only residual gap is that the routing section does not address the similarly-named sepp distribution sibling, so an agent still faces some ambiguity among closely named tools.

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

Deploy Server

Other Tools