Skip to main content
Glama

Lumpsum Calculator

lumpsum_calculator
Read-onlyIdempotent

What a one-time investment can grow to. Same calculation as https://paisafinder.com/calculators/lumpsum-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": "lumpsum_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoOne-time investment (rupees)
rateNoExpected return (p.a.) (%)
yearsNoInvestment period (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the callable-with-defaults behavior, which is genuinely useful, but says nothing about what is returned and gives no output schema to fall back on; the external URL reference is not a substitute for describing the result.

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 with the core purpose front-loaded and the optionality rule stated last where it is most actionable. The URL sentence adds little for an agent beyond a vague formula reference, but nothing is padded or redundant.

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?

For a simple three-parameter calculator with full schema coverage and read-only annotations, the definition covers the safety and defaulting story adequately. The notable gap is the absence of any statement about the response (projected corpus, growth breakdown, formatting), which matters because no output schema exists.

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 already carries units, bounds, and defaults, so the schema does the heavy lifting. The description only reiterates that omitted inputs fall back to the schema defaults, adding no extra meaning about units, compounding convention, or how the rate is applied.

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?

"What a one-time investment can grow to" clearly identifies the computed quantity (future value of a single lump-sum investment) without a named verb. It is understandable on its own, but it does not distinguish this from siblings such as compound_interest_calculator or mutual_fund_returns_calculator, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (a one-time principal growing at a rate over a period) and usefully states that every input is optional, so the agent knows it can call with zero arguments. It gives no explicit when-to-use versus when-not guidance and names no alternative for similar growth calculations.

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