Skip to main content
Glama

RD Calculator

rd_calculator
Read-onlyIdempotent

What a monthly recurring deposit pays at maturity. Same calculation as https://paisafinder.com/calculators/rd-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": "rd_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoMonthly deposit (rupees)
rateNoInterest rate (p.a.) (%). Post Office RD: 6.7%; banks: about 6-7.5%
yearsNoTenure (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rate / description
      Previous value: -"Interest rate (p.a.) (%)"New value: +"Interest rate (p.a.) (%). Post Office RD: 6.7%; banks: about 6-7.5%"
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and non-destructive, so the safety profile is fully covered. The description adds that every input is optional with defaults applied for anything omitted, plus a reference URL implying a standard, deterministic formula – modest value. It says nothing about what is actually returned (a single maturity figure? a principal/interest split?), which matters given there is no output schema.

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?

Two short sentences, front-loaded with the outcome the tool produces, and the default-filling note is tacked on at the end where it belongs. No filler or restated title.

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

Completeness3/5

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

For a simple three-param pure calculator this is nearly sufficient, but with no output schema the description should say what the result looks like (single value vs breakdown) and whether it is in rupees. As written, an agent knows how to call it but not what it will receive back.

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% and each parameter carries units, bounds, and even benchmark rates (Post Office 6.7% vs bank 6–7.5%). The description adds no parameter meaning beyond that, so the baseline 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 names the specific resource and output: the maturity payout of a monthly recurring deposit. That is enough to separate it from lumpsum/SIP/FD siblings on domain grounds, but it never mentions a sibling by name or states the distinguishing condition explicitly.

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 pointer to alternatives such as calculate_fd_maturity or project_sip, even though an agent could easily confuse an RD with a SIP. Usage is only implied by the phrase 'monthly recurring deposit'.

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