Skip to main content
Glama

Future Cash Purchasing Power

bpj_inflation_adjusted_purchasing_power
Read-onlyIdempotent

Deflate a future nominal cash target by constant annual inflation to express it in today’s purchasing power.

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": {
      "target": "<target>",
      "inflation": "<inflation>",
      "years": "<years>"
    },
    "name": "bpj_inflation_adjusted_purchasing_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYes
targetYes
inflationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds the genuine modeling assumption 'constant annual inflation', but does not disclose the compounding convention, behavior for negative rates (permitted down to -50%), or the shape of the result.

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 well-formed sentence with the operation front-loaded and no filler. It is efficiently written, though its terseness means it carries little of the disambiguation a slightly longer version could provide.

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 three-parameter arithmetic tool with no output schema, the description covers the intent but omits the formula/compounding assumption and negative-rate behavior, which are the details an agent would most need to invoke it correctly. Adequate but with clear gaps.

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 does map the three inputs semantically (target = future nominal amount, inflation = constant annual rate, years = horizon), but it never states that inflation is a percentage input or how years factor in, leaving real ambiguity.

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 ('deflate'), a specific input resource ('future nominal cash target'), and the output framing ('today's purchasing power'). An agent can tell exactly what operation is performed, though nothing distinguishes it from cash-related siblings such as bpj_cash_runway or bpj_excess_cash_sweep.

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 phrase 'future nominal ... expressed in today's purchasing power' implicitly defines the use case (converting a future nominal amount to present value under inflation), but there is no explicit when-to-use/when-not guidance and no named alternative for present-value or discounting needs.

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.