Scientific Calculator

Loan Calculator

calculator_loan

Read-only

Periodic payment, totals, and capped amortization schedule.

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": {
      "loan_amount": "<loan_amount>",
      "rate": "<rate>"
    },
    "name": "calculator_loan"
  }
}

Input Schema

Name	Required	Description	Default
`rate`	Yes	Annual interest rate %.
`tenure`	No	Tenure in years.
`loan_amount`	Yes	Loan principal.
`include_schedule`	No	Include amortization rows (capped).
`payment_frequency`	No	monthly\|quarterly\|annually etc.	monthly

Output Schema

Name	Required	Description	Default
`expression`	Yes
`periodic_payment`	Yes
`number_of_payments`	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 establish that this is a safe, read-only, non-destructive calculation. The description adds that the amortization schedule is capped and that totals are returned, which is useful behavioral context, but it does not explain the cap or any other constraints.

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 a single compact phrase with no wasted words. It is front-loaded with the key outputs, though its fragmentary form makes it slightly less clear than a full sentence.

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

Completeness3/5

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

Given that an output schema exists and the input schema fully documents all five parameters, the description need not explain return values or parameter details. However, for a calculator in a very large sibling set, it omits the usage-routing context needed to choose this tool over related loan and interest 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 description coverage is 100%, so the schema already explains rate, tenure, loan_amount, include_schedule, and payment_frequency. The description's mention of a capped amortization schedule loosely relates to include_schedule but does not add meaning beyond the schema.

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 clearly indicates the tool produces periodic payment, totals, and an amortization schedule for a loan, so the core purpose is understandable. However, it does not explicitly distinguish this tool from siblings such as calculator_emi or calculator_compound_interest.

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 gives no guidance on when to use this tool versus alternatives like calculator_emi, calculator_simple_interest, or calculator_compound_interest. It also does not state any prerequisites or exclusions.

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.