Skip to main content
Glama

Compound Growth with Contributions

bpj_compound_growth_plan
Read-onlyIdempotent

Project the balance with periodic growth followed by an end-of-period contribution.

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": {
      "opening": "<opening>",
      "contribution": "<contribution>",
      "rate": "<rate>",
      "periods": "<periods>"
    },
    "name": "bpj_compound_growth_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
openingYes
periodsYes
contributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is handled. The description does add genuine behavioral information the annotations lack: contributions are applied after growth each period, which changes the numeric result. It says nothing about what the output contains (final balance only, or a schedule) or how negative rates behave.

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?

A single well-formed sentence with no filler and the mechanics front-loaded, but it is under-specified for a four-parameter financial projection rather than genuinely concise. Nothing is wasted, yet too little is said.

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?

With no output schema, four required parameters at 0% description coverage, and no annotation-independent explanation of return values, the definition leaves key questions open: is the result one number or a period-by-period table, and is 'rate' a percent or a decimal? For a calculation tool this is a notable gap.

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

Parameters2/5

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

Schema description coverage is 0%; the schema supplies only titles. The description reinforces that the contribution is end-of-period, but says nothing about 'rate' being a percent per period (the -50 to 100 bounds hint at it), nothing about 'opening' or 'periods' semantics, and nothing about how rounding is handled.

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?

The description gives a concrete verb ('Project the balance') plus the two mechanics that define it: periodic growth and an end-of-period contribution. That ordering implicitly separates it from a plain single-period growth tool like bpj_period_growth, though it never names the alternative.

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 statement of when to use this versus a simple growth or savings-goal tool, no prerequisites, and no exclusions. The agent must infer usage purely from the mechanics described.

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.