Scientific Calculator

Simple Interest Calculator

calculator_simple_interest

Read-only

SI = (P × R × T) / 100. Returns interest and total amount.

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_simple_interest"
  }
}

Input Schema

Name	Required	Description
`rate`	Yes	Annual interest rate in %.
`time`	Yes	Time in years.
`principal`	Yes	Principal amount.

Output Schema

Name	Required	Description	Default
`interest`	Yes
`expression`	Yes
`total_amount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this as a safe, read-only, closed-world operation, so the description needn't carry the full safety burden. The formula and return summary add some computational context, but no extra behavioral details such as rounding or precision are disclosed.

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 short sentences with the formula front-loaded and no wasted text. It immediately conveys the calculation and the outputs.

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 simple three-parameter calculator with a fully documented schema, an output schema, and clear annotations, the description is nearly sufficient. It could mention rounding or precision, but those details are minor for this operation.

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% and each parameter is documented with units and examples. The description supplements this by showing the relationship between parameters through the simple interest formula, clarifying that rate is effectively treated as a percentage and time as the multiplier.

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 states a specific formula and resource: simple interest computed as SI = (P × R × T) / 100, returning interest and total amount. It is clear what the tool computes, though it does not explicitly distinguish itself from the nearby calculator_compound_interest sibling.

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 guidance on when to use this tool versus alternatives such as calculator_compound_interest, calculator_loan, or calculator_investment. The agent must infer appropriate usage from the tool name and formula alone.

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.