Skip to main content
Glama

XIRR Calculator

xirr_calculator
Read-onlyIdempotent

The real yearly return on SIPs and investments made on different dates. Same calculation as https://paisafinder.com/calculators/xirr-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": "xirr_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoMonthly investment (rupees)
finalNoFinal value (rupees)
yearsNoDuration (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 structurally. Beyond that the description adds only the defaults behavior and an external reference URL; it says nothing about what is returned, and since there is no output schema the description carries that burden and fails to pick it up. The "different dates" framing also implies a cash-flow-with-dates model that the three scalar parameters cannot express.

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?

Three short sentences, front-loaded with the purpose and then the optional-input rule; nothing is padded. The link to an external calculator is the only sentence that does not directly help an agent invoke the tool.

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?

For a computation tool with no output schema, the description should say what comes back (a rate, a percentage, a rupee amount) and it never does. Combined with the unresolved gap between "different dates" and a schema of monthly amount/final value/years, an agent cannot confidently predict the result or verify inputs map to the intended calculation.

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% with units and defaults on every property, so the baseline of 3 applies. The sentence "anything left out uses the default shown in its schema" restates what the schema's default fields already convey, so the description adds essentially no new parameter meaning.

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 computed quantity ("real yearly return") and the scenario ("SIPs and investments made on different dates"), which is more than a restatement of the name. However, it never distinguishes this from near-neighbors in the catalog that also compute SIP/return figures, and "investments made on different dates" does not match the schema, which takes a single monthly amount, a final value, and a year count with no dates at all. That mismatch leaves the agent unsure what model is actually being run.

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 versus alternatives, no preconditions, and no exclusions; the only usage-adjacent statement is that all inputs are optional and defaults apply. The agent is left to infer the choosing rule entirely from the name.

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