Skip to main content
Glama

FD ladder with your own amounts and rates

plan_fd_ladder
Read-onlyIdempotent

Maturity of a set of fixed deposits with different amounts, tenures and rates (an FD ladder), as Indian banks pay it: simple interest under 6 months, compounded quarterly from 6 months. Returns each FD's maturity and interest, and the totals. For an equal split of one amount, fd_laddering_calculator is simpler.

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": {
      "fds": "<fds>"
    },
    "name": "plan_fd_ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
fdsYesEach fixed deposit in the ladder

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral content beyond that: the interest convention (simple interest under 6 months, quarterly compounding from 6 months, as Indian banks pay it) and the shape of the result (each FD's maturity and interest, plus totals). What it does not cover is direction of rounding or whether totals include principal plus interest, which is a minor residual gap.

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?

Three short sentences, front-loaded with what the tool computes before the calculation rule and the alternative. Every sentence carries information; the parenthetical gloss of 'FD ladder' is the only slightly redundant element.

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

Completeness5/5

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

For a read-only single-parameter calculator with no output schema, the description supplies the calculation convention, the returned values, and the sibling alternative — everything an agent needs to select and call it correctly.

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%, with every nested field (amount, months, annual_interest_rate) documented including units and min/max bounds. The description only restates the three dimensions at a high level and adds no format or edge-case guidance beyond the schema, so the baseline 3 applies.

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 names the exact resource (a set of fixed deposits forming an FD ladder) and the operation (computing maturity and interest), not just the tool name restated. The phrase 'with different amounts, tenures and rates' plus the contrast with the equal-split sibling lets an agent place it precisely among the many ladder/interest calculators.

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 an explicit routing rule: for 'an equal split of one amount, fd_laddering_calculator is simpler.' That is genuine when-to-use-else guidance. It stops short of stating exclusions in the other direction (e.g., use calculate_fd_maturity for a single deposit), so it is clear but not fully exhaustive.

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