Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Compound interest calculator: future value with monthly contributions

calc_compound_interest
Read-only

Compound interest on savings or an investment: starting amount, annual rate, years, compounding (yearly, quarterly, monthly or daily) and an optional contribution at the end of each month. Returns the future value, total contributed, interest earned and the balance after each year. Use for savings goals and investment what-ifs; rates are assumed constant. Example: principal=10000, rate=7, years=10. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
rateYesAnnual interest rate in percent, -50 to 100
yearsYesYears, up to 100
monthlyNoContribution at the end of each month (default 0)
compoundNoyearly, quarterly, monthly (default) or daily
principalYesStarting amount (0 or more)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that rates are assumed constant, what the return values include, and the billing model: $0.01 per call, first 25 free, failed calls free, and repeats are not free because each call is charged. It also reinforces that the tool reads or computes only and changes nothing, which is consistent with the read-only and non-destructive annotations.

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?

The purpose and key details are front-loaded, and the paragraph is information-dense with no obvious filler. It is slightly longer than necessary because the billing model and the read-only nature are mentioned in multiple ways, but each sentence remains useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter calculator with full schema coverage and no output schema, the description is complete: it explains inputs, assumptions, return values, usage context, and billing. An agent has enough information to call it correctly without needing additional documentation.

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%, so the schema already documents all five parameters including ranges and defaults. The description restates the parameters and adds a small example but does not add meaningful syntax or format details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: compound interest calculation for savings or investments, with starting amount, annual rate, years, compounding and optional monthly contributions. It clearly distinguishes this from loan or tip calculators by framing the use case as savings goals and investment what-ifs.

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

Usage Guidelines4/5

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

It gives clear usage context: savings goals and investment what-ifs, with constant rates assumed. It does not explicitly name alternatives such as calc_loan or state when not to use it, so it lacks the explicit routing of a top score.

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.