Numeratica — financial planning calculations

roth_conversion

Multi-year Roth conversion ladder (bracket-fill, IRMAA-aware) vs. a no-conversion baseline, with a year-by-year schedule and after-tax comparison. Optional pay-tax-from-external-funds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "roth_conversion"
  }
}

Input Schema

Name	Required	Description	Default
`end_age`	No
`tax_year`	No
`birth_year`	No
`current_age`	No
`roth_balance`	No
`annual_return`	No
`filing_status`	No
`irmaa_tier_cap`	No
`state_tax_rate`	No
`target_bracket`	No
`external_return`	No
`conversion_end_age`	No
`tax_deferred_balance`	No
`other_ordinary_income`	No
`pay_tax_from_external`	No
`external_taxable_balance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: multi-year schedule, after-tax comparison, bracket-fill, IRMAA-awareness, and optional pay-tax-from-external-funds. It lacks detail on output format or data sources, but is sufficient for a simulation tool.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the core purpose, and includes a key optional feature. Every word adds value; no redundancy or filler.

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

Completeness2/5

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

Given 16 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain what the output schedule contains, how parameters interact, or what assumptions are made. The complexity demands more detail than provided.

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

Parameters2/5

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

The description mentions only one parameter ('pay tax from external funds') explicitly. With 16 parameters and 0% schema description coverage, the description fails to explain the meaning or usage of most inputs, leaving the agent to infer from parameter names alone.

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 explicitly states the tool performs a multi-year Roth conversion ladder analysis with bracket-fill and IRMAA-awareness, comparing against a no-conversion baseline. It clearly distinguishes from sibling tools like 'roth_vs_traditional' and 'retirement_backdoor_roth' by specifying the multi-year ladder aspect.

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?

The description implies usage for planning a Roth conversion ladder, but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. No exclusions or alternative tool names are mentioned.

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

All Numeratica — financial planning calculations tools Inspect

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.