Skip to main content
Glama

Fixed deposit maturity

calculate_fd_maturity
Read-onlyIdempotent

Maturity value and interest on a bank fixed deposit in India, compounded quarterly, before tax.

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": {
      "deposit": "<deposit>",
      "annual_interest_rate": "<annual_interest_rate>",
      "tenure_years": "<tenure_years>"
    },
    "name": "calculate_fd_maturity"
  }
}

Input Schema

NameRequiredDescriptionDefault
depositYesDeposit amount in rupees
tenure_yearsYesTenure in years
annual_interest_rateYesFD rate, % per year

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, non-destructive and closed-world, so the safety profile is covered. The description adds genuine domain behavior beyond them: quarterly compounding frequency, pre-tax basis, and India-specific scope. It does not say anything about rounding, payout assumptions, or how interest is reported.

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?

A single front-loaded phrase with zero filler, leading with the two outputs the caller cares about. It is slightly under-specified as a sentence fragment, but nothing in it is wasted.

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 3-parameter, fully-required calculator with complete schema coverage and no output schema, the description covers the essentials: what is computed, the compounding convention, and the pre-tax scope. It is still missing routing guidance against the many sibling calculators and any note on result interpretation, which keeps it at minimum-viable rather than complete.

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 parameter documented including units and min/max bounds, so the schema carries the parameter burden. The description adds only the compounding convention that implicitly governs how annual_interest_rate is applied, which is useful but not parameter-level detail.

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 resource (bank fixed deposit in India) and the two outputs computed (maturity value and interest), plus the key modeling assumption of quarterly compounding. It omits an explicit verb and never distinguishes itself in words from close siblings like rd_calculator or compound_interest_calculator, 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 Guidelines2/5

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

There is no statement of when to use this tool versus alternatives such as rd_calculator (recurring deposits) or compound_interest_calculator, and no exclusions or prerequisites are given. The 'before tax' note hints at a boundary but is not framed as usage guidance.

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