Skip to main content
Glama

SWP Calculator

swp_calculator
Read-onlyIdempotent

Monthly income from your mutual funds, and how long it lasts. Same calculation as https://paisafinder.com/calculators/swp-calculator. Every input is optional; anything left out uses the default shown in its schema.

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": "swp_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoStarting corpus (rupees)
incNoRaise the withdrawal every year by (%). To keep up with inflation, try 5-6%; 0 = same amount every year
rateNoExpected return (p.a.) (%)
yearsNoDuration (years)
withdrawNoMonthly withdrawal (rupees)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / inc
      Added value: +{
      +  "default": 0,
      +  "description": "Raise the withdrawal every year by (%). To keep up with inflation, try 5-6%; 0 = same amount every year",
      +  "maximum": 15,
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the tool computes rather than mutates data. The description adds real value by stating that all inputs are optional and defaults are applied; however, with no output schema it never says whether the result is a single number, a yearly schedule, or a depletion horizon, leaving the response shape undisclosed.

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 most useful content, what is computed, is front-loaded in one clause, followed by the default-handling note. The middle sentence is essentially a URL citation that adds mild fidelity context but little operational value; overall it is tight with no padding.

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 5-parameter, all-optional, no-output-schema calculator, the description covers the purpose, the output concept (income amount and duration), and the defaulting rule. The remaining gap is the precise return structure and units, which an agent would need to interpret results without an output schema.

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 coverage is 100% and the schema descriptions are strong on their own (for example the 'inc' parameter explains the 5-6% inflation-tracking hint). The description only restates the default-fallback behavior, which is already derivable from the declared defaults, so it adds little meaning beyond the schema and the baseline of 3 applies.

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 states what the tool computes in concrete terms: monthly income from a mutual fund corpus and how long that corpus lasts, reinforced by the reference to the paisafinder SWP calculator page. The purpose is clear, but the description never distinguishes it from nearby siblings such as lumpsum_calculator, project_sip, or retirement_calculator, and never states that this is a systematic-withdrawal-plan calculation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only usage-adjacent sentence is 'Every input is optional; anything left out uses the default shown in its schema', which explains how to call it rather than when to choose it over the other calculator tools.

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