Skip to main content
Glama

Inherited IRA plan

inherited_ira_plan
Read-onlyIdempotent

Work out the distribution rules for an inherited IRA under the SECURE Act final regulations (T.D. 10001) and IRS Pub. 590-B: the beneficiary class (eligible designated, designated or non-designated), whether the owner died before or after the required beginning date, the rule that applies (life expectancy, 10-year with or without annual RMDs, 5-year), the deadline to empty the account, this year's required minimum from the Single Life Expectancy Table, and four ways to drain it (back-loaded, even, front-loaded, fill a bracket) compared on federal tax in 2026 dollars and after-tax value. No names or account numbers are 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": {
      "beneficiaryClass": "<beneficiaryClass>",
      "ownerBirthYear": "<ownerBirthYear>",
      "ownerDeathDate": "<ownerDeathDate>",
      "balance": "<balance>"
    },
    "name": "inherited_ira_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
rothNoTrue for an inherited Roth IRA.
yearNoPlan year (default 2026).
balanceYesAccount balance on December 31 of the prior year.
fillRateNoBracket to fill each year in the fill strategy (default 24).
realReturnNoAnnual return after inflation in percent (default 0).
otherIncomeNoBeneficiary's other ordinary income per year (default 0).
electTenYearNoEligible beneficiary elected the 10-year rule (owner died before the required beginning date).
filingStatusNoBeneficiary's filing status (default single).
stateTaxRateNoFlat state tax rate in percent (default 0).
takenThisYearNoDistributions already taken this year (default 0).
ownerBirthYearYesOriginal owner's birth year.
ownerDeathDateYesOwner's date of death, YYYY-MM-DD (or a year).
beneficiaryClassYesspouse = Surviving spouse; minor_child = Owner’s child under 21; disabled = Disabled; chronically_ill = Chronically ill; close_in_age = Not more than 10 years younger than the owner; designated = Other person (designated beneficiary); non_designated = Estate, charity or non-qualifying trust.
beneficiaryBirthYearNoBeneficiary's birth year (not needed for non_designated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world calculation with no destructive side effects. The description adds meaningful behavioral context: the regulatory basis, the categories and rules it evaluates, the outputs it computes, and the privacy note that no identifying data is needed. It does not spell out computational assumptions such as tax treatment details, but it goes well beyond the annotations.

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 description is a single dense sentence but is front-loaded with the core purpose and then enumerates outputs efficiently. Every clause contributes to understanding the calculation, though the run-on structure could be easier to scan.

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?

For a complex 14-parameter financial calculator with no output schema, the description does a good job listing the key outputs: beneficiary class, applicable rule, deadline, current RMD, and strategy tax comparisons. It could say more about output format or modeling assumptions, but it is substantially complete.

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 14 parameters thoroughly. The description adds high-level meaning around beneficiary class, death before/after the required beginning date, this year's RMD, and the four withdrawal strategies, but it does not explain most individual parameters beyond what the schema provides. Baseline 3 is appropriate.

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 gives a specific verb-resource scope: it works out inherited IRA distribution rules under the SECURE Act and Pub. 590-B. It distinguishes itself from siblings like retirement_plan or roth_conversion_plan by focusing narrowly on inherited IRA beneficiary rules, deadlines, RMDs, and withdrawal strategies.

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?

The description makes clear this is for inherited IRA distribution planning under the SECURE Act, so an agent can infer when to use it. It does not explicitly name alternatives or exclusions, but the context and the note that no names or account numbers are needed provide useful usage framing.

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