Skip to main content
Glama

Compound Interest

compound_interest_calculator
Read-onlyIdempotent

How interest earns interest over the years. Same calculation as https://paisafinder.com/calculators/compound-interest-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": "compound_interest_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoPrincipal (rupees)
freqNoInterest added: 1 = Yearly, 2 = Half-yearly, 4 = Quarterly, 12 = Monthly
rateNoRate (p.a.) (%)
yearsNoTime (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / freq / description
      Previous value: -"Compounding/yr. 1=annual · 2=half-yr · 4=quarterly · 12=monthly"New value: +"Interest added: 1 = Yearly, 2 = Half-yearly, 4 = Quarterly, 12 = Monthly"
    • addedInput schema / properties / freq / enum
      Added value: +[
      +  1,
      +  2,
      +  4,
      +  12
      +]
    • removedInput schema / properties / freq / maximum
      Removed value: -12
    • removedInput schema / properties / freq / minimum
      Removed value: -1
  2. First observed

TDQS

B3.1/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 safety and determinism are covered. The description adds genuine value by clarifying that omitted inputs fall back to schema defaults, but it says nothing about the returned result or whether a year-by-year breakdown is included.

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?

Two short sentences, front-loaded with the concept, then the defaults rule. The external URL is of marginal use to an agent and adds a little noise, but overall there is little wasted text.

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 read-only calculator with no output schema, an agent still needs to know what comes back (final maturity value, total interest, compounding schedule). Annotations cover the safety profile and parameters are fully documented, but the result shape is left unstated.

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 defaults, bounds and an enum already documented, so the baseline is 3. The description's note that anything left out uses its schema default adds a small but real clarification about omission semantics rather than merely restating fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains the concept ("how interest earns interest over the years") but never states a concrete verb such as "calculate" or what the tool returns. It also does nothing to separate it from close siblings like simple_interest_calculator or cagr_calculator, which an agent could easily confuse with this one.

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?

The only usage-type guidance is that all inputs are optional and defaults apply, which is a calling convention rather than a when-to-use rule. There is no statement of when this is preferable to the simple-interest or CAGR siblings, nor any exclusions.

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