Skip to main content
Glama

CAGR Calculator

cagr_calculator
Read-onlyIdempotent

Average yearly growth between a start and an end value. Same calculation as https://paisafinder.com/calculators/cagr-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": "cagr_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd value (rupees)
startNoStart value (rupees)
yearsNoDuration (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the default-substitution contract, which is real behavioral value beyond annotations, but says nothing about what the tool returns (a percentage per annum? a multiple?) even though no output schema exists to fill that gap.

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 the core definition, then the default-handling rule. The external URL reference is arguably promotional rather than functional, but it does anchor expected behavior for a well-known calculation.

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 3-param, no-output-schema calculator the agent still needs to know the shape of the answer and its units/rounding to report results correctly; the description omits both. The default-substitution rule and the reference implementation cover input behavior adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and all three parameters carry units, defaults and bounds, so the baseline is 3. The description adds meaning beyond the schema by explaining the missing-value contract, though it does not clarify the units of the result or how a fractional `years` input is interpreted.

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 specific computation: "Average yearly growth between a start and an end value", which identifies the CAGR operation and the two anchor values. It does not, however, distinguish itself from close siblings such as roi_calculator, lumpsum_calculator, or xirr_calculator, which also compute growth rates, so the 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 line "Every input is optional; anything left out uses the default shown in its schema" gives useful calling guidance about defaults, which is genuinely operative information. There is no when-to-use/when-not guidance relative to the growth-rate siblings, and no statement about what assumptions the calculation makes (e.g. annual compounding).

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