Skip to main content
Glama

Investment Calculator

calculator_investment
Read-only

Growth of initial investment plus regular contributions.

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": {
      "initial_investment": "<initial_investment>",
      "rate": "<rate>",
      "years": "<years>"
    },
    "name": "calculator_investment"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYesExpected annual return %.
yearsYesDuration in years.
initial_investmentYesStarting principal.
regular_contributionNoContribution per compounding period.
compounding_frequencyNoCompounding frequency.annually

Output Schema

NameRequiredDescriptionDefault
expressionYes
final_valueYes
total_investedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already establish read-only, closed-world, non-destructive behavior, so the safety profile is covered. The description adds nothing beyond that: it does not say whether contributions are treated as end-of-period or beginning-of-period, whether rate is nominal or effective, or any other computational convention an agent would need to trust 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with no filler, which is good, but it is an under-specified sentence fragment rather than a complete statement of purpose. Brevity here comes at the cost of the information an agent needs.

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?

An output schema exists and all parameters are documented, so return values and inputs are covered. However, for a calculator that sits among multiple overlapping finance tools, the description never resolves which one to choose, leaving the single most important contextual gap unaddressed.

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 per-property descriptions and examples for all five parameters, so the baseline is 3. The description merely restates 'initial investment' and 'regular contributions' and adds no meaning about compounding timing or negative-value handling beyond the schema.

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 fragment 'Growth of initial investment plus regular contributions' identifies the computed quantity, but it is a noun phrase with no verb and does not distinguish this tool from near-identical siblings such as calculator_compound_interest, calculator_sip, and calculator_cagr. In a sibling set of ~140 calculators, that differentiation gap matters.

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 indication of when to use this tool versus the closely competing compound-interest, SIP, or simple-interest calculators, and no prerequisites or exclusions are stated. The agent is left to infer selection entirely from the title.

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.