Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

math_compound_interest_calculator

Read-onlyIdempotent

Calculate the future value of a lump-sum investment with compound interest and recurring contributions. Get final balance, total interest, and per-period breakdown.

Instructions

Compound Interest Calculator. Project the future value of a lump-sum principal growing at a fixed annual rate with periodic (per-compounding-period) compounding and optional recurring contributions. Returns the final balance, total interest earned, total contributions, and a per-period or per-year breakdown. Use this for savings/investment growth ("how much will X grow to in N years"); use math_loan_calculator instead when you owe a balance and need a monthly payment + amortization schedule, or math_percentage_calculator for one-off percent-of / percent-change math. Pure local arithmetic: read-only, non-destructive, deterministic, contacts no external service, and is rate-limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNo"compute" returns a per-year breakdown (one row per year); "schedule" returns the full per-period schedule (one row per compounding period). Both return the same final totals.compute
principalYesStarting lump-sum amount (P). 0 to 1,000,000,000,000.
annualRatePercentYesNominal annual interest rate as a percent (e.g. 5 means 5%/yr). 0 to 100.
yearsYesInvestment horizon in years (t). Greater than 0, up to 100; may be fractional.
compoundingsPerYearYesCompounding frequency per year (n): 1=annual, 2=semi-annual, 4=quarterly, 12=monthly, 365=daily. Must be exactly one of these values.
monthlyContributionNoOptional recurring monthly contribution. Converted to a per-compounding-period amount (monthlyContribution × 12 / compoundingsPerYear) so the same annual dollar flow applies at any frequency. 0 to 1,000,000,000.
contributionTimingNoWhether each contribution is applied at the start (annuity-due) or end (ordinary annuity) of the period. Only relevant when monthlyContribution > 0.end

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the calculation succeeded.
operationNoEchoes the operation that was run.
resultNoComputed totals plus a breakdown (compute) or schedule (schedule) array.
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent. The description adds 'deterministic', 'contacts no external service', and 'rate-limited', providing useful context beyond annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

5 sentences, no fluff. Front-loads purpose, then output, usage guidelines, and behavioral traits. Every sentence earns its place. Highly efficient.

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?

Given the tool's moderate complexity with 7 parameters and existing output schema, the description covers purpose, usage, behavior, and output summary. No gaps remain for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for each parameter. The description adds value by summarizing outputs (final balance, interest, etc.) and explaining operation parameter semantics. This goes beyond baseline 3.

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 clearly states the tool's purpose: projecting future value of a lump-sum with fixed rate, periodic compounding, and optional contributions. It distinguishes itself from siblings like math_loan_calculator and math_percentage_calculator, making scope explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly provides when-to-use (savings/investment growth) and when-not-to-use (use math_loan_calculator for loans, math_percentage_calculator for percent calculations). This leaves no ambiguity for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server