Skip to main content
Glama

Multi-Period Growth

bpj_period_growth
Read-onlyIdempotent

Compare starting and ending values and calculate compound growth per period.

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": {
      "start": "<start>",
      "end": "<end>",
      "periods": "<periods>"
    },
    "name": "bpj_period_growth"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
periodsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 fully covered and the description does not need to restate it. What the description does add is the computational semantics (growth derived across periods), but it omits anything about how zero or near-zero start values are handled, and whether the result is a rate, a percentage, or a value series.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently structured, though the brevity is close to under-specification rather than true conciseness.

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?

For a three-parameter calculator with no output schema, the description should say what comes back (a per-period rate, a total multiple, etc.) and what the period unit means. Neither is present, and no edge-case behavior is disclosed, so an agent can invoke the tool but cannot confidently predict or interpret its result.

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 parameters carry only titles ("Starting value", "Ending value", "Number of periods") with no explanatory text. The description references start, end, and periods only obliquely and adds no units, no expected format for the period count (days? years? months?), and no hint about the enforced minimum start of 0.000001. With low coverage, the description needed to compensate and does not.

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?

"Compare starting and ending values and calculate compound growth per period" names a specific verb pair (compare/calculate) and resource (compound growth over periods), so an agent knows this is a growth-rate calculator rather than a validator or formatter. It does not distinguish itself from the closely named sibling bpj_compound_growth_plan, leaving the boundary between the two for the agent to guess.

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 tool versus alternatives, no prerequisites, and no exclusions. The agent must infer from the name alone that this is a plain two-point CAGR computation rather than a multi-scenario planning tool like bpj_compound_growth_plan.

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.