Scientific Calculator

Compound Interest Calculator

calculator_compound_interest

Read-only

A = P(1+r/n)^(nt). Supports annually, half-yearly, quarterly, monthly, daily.

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": {
      "principal": "<principal>",
      "rate": "<rate>",
      "time": "<time>"
    },
    "name": "calculator_compound_interest"
  }
}

Input Schema

Name	Required	Description	Default
`rate`	Yes	Annual rate %.
`time`	Yes	Time in years.
`principal`	Yes	Principal amount.
`compounding_frequency`	No	annually\|half-yearly\|quarterly\|monthly\|daily or n/year.	annually

Output Schema

Name	Required	Description	Default
`expression`	Yes
`final_amount`	Yes
`compound_interest`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world calculation. The description adds useful computational behavior: the compound-interest formula and the supported compounding periods. It does not discuss rounding or rate interpretation, but those are partly covered by the schema and output schema.

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?

Two compact sentences with no filler. The core formula is front-loaded and the supported frequencies follow immediately.

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?

For a pure calculator with full schema descriptions and an output schema, the description covers the core computation and compounding options adequately. The main gap is the lack of guidance about when to choose this over similar financial calculators.

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 all four parameters are already described. The description's formula maps P, r, n, and t conceptually to the inputs, but it adds little beyond the schema, which already defines principal, annual rate %, time in years, and compounding frequency.

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 gives the exact compound-interest formula and lists supported compounding frequencies, making the operation clear. It does not explicitly distinguish itself from nearby siblings such as calculator_simple_interest, calculator_cagr, or calculator_investment, so it stops short of full sibling differentiation.

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?

The description explains the formula but gives no guidance on when to use this tool versus simple interest, CAGR, investment, or loan calculators. The frequency list is parameter detail, not usage guidance.

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

All Scientific Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.