Scientific Calculator

SIP Calculator

calculator_sip

Read-only

Monthly SIP maturity using FV = M((1+i)^n−1)/i.

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": {
      "monthly_investment": "<monthly_investment>",
      "rate": "<rate>"
    },
    "name": "calculator_sip"
  }
}

Input Schema

Name	Required	Description
`rate`	Yes	Expected annual return %.
`tenure`	No	Duration in years.
`tenure_months`	No	Duration in months.
`monthly_investment`	Yes	Monthly SIP amount.

Output Schema

Name	Required	Description	Default
`expression`	Yes
`maturity_value`	Yes
`total_invested`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already establish readOnly/non-destructive/closed-world, so safety needs no restating. The formula does add real behavioral content by revealing the annuity-due convention (the trailing (1+i) factor, i.e. contributions at period start), but the description never says how the annual 'rate' % becomes i on a monthly basis or how tenure and tenure_months are reconciled.

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 sentence with zero filler, and the formula is the most information-dense thing it could include. It is under-specified rather than padded, which is a completeness issue, not a verbosity one.

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

Completeness2/5

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

An output schema exists, so return values need no explanation. But for a finance calculator with 4 parameters (2 required, 2 overlapping time inputs), the description omits the compounding-frequency convention, the tenure vs tenure_months precedence, and any routing guidance among the many finance siblings.

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%, so baseline is 3. The formula's M/i/n symbols loosely map to monthly_investment/rate/tenure, but they do not resolve the key ambiguity: whether n is years or months, and what happens when both tenure and tenure_months are supplied (only monthly_investment and rate are required).

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 names the resource ('Monthly SIP maturity') and gives the exact formula used, which does distinguish it mathematically from generic compound-interest or investment calculators. However it is a noun phrase with no verb and no explicit statement of what the tool returns, leaving the intended action only implied.

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 when-to-use or when-not-to-use guidance at all. In a sibling set containing calculator_compound_interest, calculator_investment, calculator_emi, and calculator_simple_interest, an agent gets no help deciding which of these overlapping finance tools to call.

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.