Skip to main content
Glama
Sign In

Amaltash Investment & Retirement Calculators

by com.amaltash
OverviewDiscussionsAdmin

Retirement Calculator

retirement_plan
Read-onlyIdempotent

Retirement calculator with an interactive chart of the balance by age. Replays a plan through every complete stretch of real US market history since 1928 and reports how often the money lasted. Use it when the monthly spending is known, for questions like can I retire at 60, or how long will my savings last.

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": {
      "age": "<age>",
      "retire_age": "<retire_age>",
      "end_age": "<end_age>",
      "savings": "<savings>",
      "save_monthly": "<save_monthly>",
      "other_income": "<other_income>",
      "stock": "<stock>",
      "spend_monthly": "<spend_monthly>"
    },
    "name": "retirement_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesAge today, in whole years, from 18 to 100.
stockYesShare held in stocks, from 0 to 1. The rest is in 10-year US Treasuries.
end_ageYesAge the money must last to. It must be above retire_age, and the span from age must fit in the data since 1928.
savingsYesMoney saved so far, in US dollars.
retire_ageYesAge when saving stops and spending starts. It cannot be below age.
other_incomeYesMonthly income in retirement from other sources, such as Social Security, in today's dollars.
save_monthlyYesDollars added each month until retirement.
spend_monthlyYesMonthly spending in retirement, in today's dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive calculation. The description adds meaningful behavioral context beyond that: it replays every complete stretch of real US market history since 1928 and reports how often the money lasted, plus an interactive chart. It does not detail return structure or assumptions, but the historical-simulation behavior is well disclosed.

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 short and front-loaded, first identifying the tool and then giving the historical simulation behavior and use cases. The opening phrase restates the title somewhat, but overall it is efficient and readable.

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 an eight-parameter calculator with full schema coverage and no output schema, the description does a good job explaining the simulation method and the two main outputs. It could be more complete by describing assumptions or the exact result structure, but nothing critical is missing for correct invocation.

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 input schema already defines all eight parameters with ranges and meanings. The description adds conceptual context about monthly spending and historical market replay but does not explain individual parameters beyond what the schema provides, making 3 the appropriate baseline.

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 a specific tool type (retirement calculator), explains the core computation (replaying plans through real US market history since 1928), and describes the outputs (balance-by-age chart and success rate). It does not explicitly distinguish itself from overlapping siblings such as safe_spending or sequence_risk, so it stops short of a 5.

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 clear when-to-use guidance: when monthly spending is known, for questions like retiring at 60 or how long savings will last. It does not mention when not to use it or name alternative tools for related questions, which keeps it below a 5.

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

All Amaltash Investment & Retirement Calculators 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