Skip to main content
Glama

Growing Perpetuity Value

bpj_growing_perpetuity_value
Read-onlyIdempotent

Estimate the current value of a growing perpetuity using next year’s cash flow and a discount rate above growth.

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": {
      "next": "<next>",
      "discount": "<discount>",
      "growth": "<growth>"
    },
    "name": "bpj_growing_perpetuity_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextYes
growthYes
discountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety and side-effect behavior are fully covered by structured data. The description adds only the mathematical validity condition (discount > growth); it does not say what happens if that condition is violated, nor what the response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single front-loaded sentence naming the verb, the resource, and the inputs, with no filler or restatement of the title. Every clause carries information.

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 pure calculation tool with no output schema, the description never states the output form (a single monetary amount) or the failure behavior when growth meets or exceeds the discount rate. The essential formula inputs are present, but an agent still has to infer the return shape.

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 0%, so the description must compensate; it references the cash flow and discount rate but omits 'growth' as a named input. Its one genuine addition is the relational constraint that discount must exceed growth, which the schema does not encode. Units and formatting are left to the schema titles.

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 verb ('Estimate') and resource ('current value of a growing perpetuity') plus the inputs used. The constraining condition 'discount rate above growth' further narrows what the tool computes. It does not reference any sibling, but the operation is self-contained enough that an agent can recognize it as a finance valuation calculator.

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 clause 'a discount rate above growth' implicitly tells the agent when the formula is valid, which is real guidance. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative among the many sibling valuation tools.

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.