Skip to main content
Glama

Compound Interest Calculator API - growth with monthly deposits

compound_interest_calculator
Read-onlyIdempotent

Final balance, total deposits and interest earned with yearly rate, years, optional monthly deposit and compounding frequency, plus the year-by-year table. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/compound-interest-calculator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "years": 10,
      "ratePercent": 5,
      "startAmount": 10000,
      "monthlyDeposit": 200
    },
    "name": "compound_interest_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoYears
compoundingNoTimes per year: 12, 4, 1 or 36512
ratePercentNoYearly interest rate in %
startAmountNoStarting amount
monthlyDepositNoAdd every month (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / years / minimum
      Added value: +0
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint/openWorldHint annotations, the description adds genuinely useful operational context: 25 calls/day per IP on the free tier, $0.001 per call via x402, and that nothing is stored after the call. The 'files are deleted right after the call' claim is slightly incongruous for a parameterless-file calculator, but the rate-limit and cost disclosure is the kind of information annotations cannot carry.

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 compact sentences, front-loaded with what comes back and then the operational facts; nothing is padded. The pricing URL is long but earns its place by letting an agent reason about cost.

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

Completeness4/5

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

There is no output schema, and the description compensates by naming the four returned values, which is what an agent needs to chain this tool. It stops short of describing the shape of the year-by-year table, and the five parameters are fully covered by the schema, so completeness is strong but not exhaustive.

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 coverage is 100%, so every parameter already has a description, including the enum values for compounding. The description restates those fields at a high level (yearly rate, years, optional monthly deposit, compounding frequency) without adding format, unit, or boundary meaning 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.

Purpose4/5

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

The description names the concrete outputs (final balance, total deposits, interest earned, year-by-year table) and the inputs that drive them (yearly rate, years, monthly deposit, compounding frequency), so an agent knows exactly what computation happens. It does not name or differentiate itself from the plausible sibling loan_calculator, which is the main gap.

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?

Usage is implied by the enumerated inputs and outputs, but there is no explicit statement of when to use this instead of loan_calculator or percentage_calculator, and no when-not-to-use guidance. The free-tier and x402 pricing notes tell the agent about cost, not about tool selection.

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