Skip to main content
Glama

FD Laddering

fd_laddering_calculator
Read-onlyIdempotent

Split money into FDs that mature every month, quarter or year. Same calculation as https://paisafinder.com/calculators/fd-laddering-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": "fd_laddering_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoInterest rate (p.a.) (%). Big banks about 6.5-7.3%; small finance banks up to about 8%
rungsNoNumber of FDs
totalNoTotal amount to deposit (rupees)
gapMonthsNoGap between FDs. 1 = one FD a month, 3 = every quarter, 12 = every year
firstMonthsNoFirst FD tenure. 12 = 1 year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / firstMonths
      Added value: +{
      +  "default": 12,
      +  "description": "First FD tenure. 12 = 1 year",
      +  "maximum": 120,
      +  "minimum": 1,
      +  "type": "number"
      +}
    • addedInput schema / properties / gapMonths
      Added value: +{
      +  "default": 12,
      +  "description": "Gap between FDs. 1 = one FD a month, 3 = every quarter, 12 = every year",
      +  "maximum": 36,
      +  "minimum": 1,
      +  "type": "number"
      +}
    • removedInput schema / properties / minYr
      Removed value: -{
      -  "default": 1,
      -  "description": "First rung tenure (years)",
      -  "maximum": 5,
      -  "minimum": 1,
      -  "type": "number"
      -}
    • changedInput schema / properties / rate / description
      Previous value: -"Interest rate (p.a.) (%). Typical small-finance bank: 7.5–8%"New value: +"Interest rate (p.a.) (%). Big banks about 6.5-7.3%; small finance banks up to about 8%"
    • changedInput schema / properties / rungs / description
      Previous value: -"Number of rungs"New value: +"Number of FDs"
    • changedInput schema / properties / rungs / maximum
      Previous value: -10New value: +24
    • removedInput schema / properties / spread
      Removed value: -{
      -  "default": 1,
      -  "description": "Spread between rungs (years). Years between each maturity",
      -  "maximum": 3,
      -  "minimum": 1,
      -  "type": "number"
      -}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the defaults-fallback behavior and points to an external reference for calculation parity, but never says what comes back (a maturity schedule, a table of rungs, amounts per FD), which is the one behavior an agent cannot infer.

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 the core operation and free of filler. The external URL is marginally useful as a calculation-parity reference but is the one element that could be trimmed.

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?

With five fully documented parameters and rich annotations, most of the structured burden is already carried, and there is no output schema to explain. Still, for a calculator whose entire value is the returned ladder schedule, the absence of any statement about output shape leaves a real gap.

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 the schema itself carries units, ranges, defaults, and interpretive hints for every parameter, so the baseline of 3 applies. The description only redirects to the schema for defaults and adds no extra meaning about how rate, rungs, gapMonths, and firstMonths interact.

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?

"Split money into FDs that mature every month, quarter or year" gives a specific verb (split), resource (FDs), and outcome (staggered maturities), so the operation is unambiguous. It does not differentiate itself from the close sibling plan_fd_ladder or calculate_fd_maturity, leaving the agent to guess which of the three to pick.

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?

It usefully states that every input is optional and omitted inputs fall back to schema defaults, which tells the agent it can call with zero arguments. However, it offers no when-to-use guidance against the laddering-adjacent siblings, which is the main ambiguity an agent faces here.

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