Skip to main content
Glama

Equal Cash Flow Project NPV

bpj_equal_cashflow_project_npv
Read-onlyIdempotent

Discount equal year-end cash flows and subtract the time-zero investment to calculate net present value.

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": {
      "outlay": "<outlay>",
      "flow": "<flow>",
      "years": "<years>",
      "discount": "<discount>"
    },
    "name": "bpj_equal_cashflow_project_npv"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowYes
yearsYes
outlayYes
discountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a safe, read-only, idempotent, closed-world calculation, so the description carries a lighter burden. It does add genuine behavioral content by fixing timing conventions: flows occur at year-end and the outlay sits at time zero (thus undiscounted). It stops short of stating sign conventions or how the discount rate is expressed, so the added value is real but limited.

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 well-formed sentence with the computation front-loaded and no redundant phrasing. Every clause contributes (year-end timing, time-zero subtraction, the result) and nothing could be cut without losing meaning.

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 four-parameter pure calculation with no output schema and annotations already covering safety, the description supplies the core formula semantics but omits conventions an agent would want: rate units beyond the schema title, sign handling for negative flows, and confirmation that all four inputs are mandatory. Adequate, not complete.

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, and it partially does: it maps 'outlay' to a time-zero investment and 'flow' to equal year-end cash flows, clarifying the timing model behind the bare schema titles. It leaves 'years' implicit and never restates that the rate is a percentage or how negative flows behave, so meaningful gaps remain.

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 names a specific computation: discounting equal year-end cash flows and subtracting the time-zero investment to yield net present value. The 'equal year-end cash flows' qualifier identifies it as an annuity-style NPV, which separates it from general or irregular cash-flow tools. It does not explicitly contrast with any named sibling, keeping it just below a 5.

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 explicit statement of when to use this tool versus alternatives, and no prerequisites or exclusions are given. The annuity wording implicitly scopes usage to level, year-end flows, but the agent must infer that rather than being told.

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.