Scientific Calculator

EMI Calculator

calculator_emi

Read-only

Monthly EMI, total payment, and total interest. Handles 0% rate.

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>"
    },
    "name": "calculator_emi"
  }
}

Input Schema

Name	Required	Description
`rate`	Yes	Annual interest rate %.
`tenure`	No	Tenure in years (or use tenure_months).
`principal`	Yes	Loan principal.
`tenure_months`	No	Tenure in months (alternative).

Output Schema

Name	Required	Description	Default
`emi`	Yes
`expression`	Yes
`total_payment`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.2/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. The description adds one useful behavioral detail, that it handles 0% rate, but does not disclose other behavioral traits such as rounding, assumptions, or formula details.

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?

The description is only two short sentences with no wasted words, and it front-loads the outputs. However, it is written as sentence fragments rather than a fully structured explanation.

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 calculator with rich schema coverage and an output schema, the description is largely complete: it lists the key results and notes a notable edge case. It could still improve by stating usage context and sibling differentiation, but nothing critical for invocation is missing.

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 all four parameters are already documented in the schema. The description does not add meaning beyond the schema, apart from implicitly referencing the rate parameter through the 0% case.

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 identifies the specific outputs of an EMI calculation: monthly EMI, total payment, and total interest. It is clear enough from the tool name/title and output list, but it lacks an explicit verb and does not differentiate itself from potentially overlapping siblings such as calculator_loan.

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?

It gives no guidance on when to use this tool versus alternatives like calculator_loan or calculator_simple_interest. The only usage-adjacent statement is 'Handles 0% rate,' which is an edge-case behavior rather than a selection rule.

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.