Skip to main content
Glama

Free Cash After Capital Spending

bpj_free_cash_after_capex
Read-onlyIdempotent

Subtract capital spending from operating cash flow to estimate free cash flow for the 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": {
      "operatingCash": "<operatingCash>",
      "capex": "<capex>"
    },
    "name": "bpj_free_cash_after_capex"
  }
}

Input Schema

NameRequiredDescriptionDefault
capexYes
operatingCashYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and determinism profile is covered. The description adds that this is a derivation (a subtraction), which confirms pure computation with no side effects, but says nothing beyond that about the result's form or units.

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?

One sentence, front-loaded with the operation and inputs, with no filler or repetition. 'For the period' is slightly redundant but harmless.

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?

With no output schema, the description should clarify what the caller receives (a single scalar in a stated currency), and it only implies this. For a two-parameter deterministic calculator the essentials are present, but units and result framing are missing.

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 is the only source of meaning, and it does supply the key semantic the schema lacks: the two numbers are combined by subtraction, giving capex a negative sign in the free-cash-flow result. However, it omits units/currency, scaling, and how a negative operating cash flow behaves, so it does not fully compensate for the coverage gap.

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?

Specific verb (subtract) plus named inputs and output (free cash flow), so the agent knows exactly what computation happens and what it yields. It does not explicitly differentiate from nearby siblings like bpj_operating_working_capital_change or bpj_cash_runway, but the formula itself makes the scope unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. Usage is only implied by the arithmetic itself ('free cash flow for the period'), which is adequate for a self-contained calculator but leaves the agent to infer context.

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.