Skip to main content
Glama

ROI Calculator

roi_calculator
Read-onlyIdempotent

How much an investment gained, in total and per year. Same calculation as https://paisafinder.com/calculators/roi-calculator. Every input is optional; anything left out uses the default shown in its schema.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "roi_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoAmount invested (rupees)
finalNoFinal value (rupees)
yearsNoDuration (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds two genuinely useful behavioral facts: the output is a total figure plus an annualized figure, and partial invocations are legal with documented defaults. It does not say how a negative or zero-loss result is reported, which matters since no output schema exists.

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?

Two short sentences, front-loaded with what is computed before the optionality note. The paisafinder.com URL is defensible because it pins the exact formula rather than restating behavior, though it is the one element an agent cannot act on directly.

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 three-parameter, annotation-rich, output-schema-less calculator the definition covers intent, units via the schema, and default behavior. The remaining gap is the shape of the returned values (field names, sign convention, rounding), which the description gestures at but does not specify.

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% and each parameter carries units, ranges and defaults (amount invested, final value in rupees, duration in years). The description adds only the cross-cutting rule that every field is optional with defaults, which is a small increment over the schema. Baseline 3 is appropriate.

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?

States a concrete computation — total gain and gain per year on an investment — with a verb-equivalent ('how much an investment gained') and a scoped output, so an agent knows it produces returns rather than a rate. It never contrasts itself with the many overlapping siblings (cagr_calculator, lumpsum_calculator, xirr_calculator), so differentiation is left to inference.

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 only guidance is about invocation mechanics: all inputs are optional and omitted ones fall back to schema defaults. There is no statement of when this tool is the right choice versus the dozens of adjacent return/interest calculators in the sibling list, and no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources