Skip to main content
Glama

Cash Runway

bpj_cash_runway
Read-onlyIdempotent

Estimate months of runway from a cash balance and constant monthly income and spending.

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": {
      "cash": "<cash>",
      "inflow": "<inflow>",
      "outflow": "<outflow>"
    },
    "name": "bpj_cash_runway"
  }
}

Input Schema

NameRequiredDescriptionDefault
cashYes
inflowYes
outflowYes

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 this a safe, idempotent, closed-world read, so the safety profile needs no restating. The description does add real modeling context by stating the flows are treated as 'constant' (a linear, no-growth, no-interest projection), but it omits the degenerate cases an agent would care about, such as zero or negative net burn and how runway is reported in those situations.

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 front-loaded sentence with no filler; the computed quantity and its inputs come first. It is efficient, though the terseness leaves no room for the small amount of edge-case framing the tool would benefit from.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter deterministic calculator with full annotation coverage, the core definition is essentially complete. Since no output schema exists, the description could have stated the return unit (months, and how rounding or an infinite runway is expressed), which is the one remaining gap.

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% — only short titles exist — so the description must carry the meaning, and it does map all three parameters conceptually (cash -> cash balance, inflow -> monthly income, outflow -> monthly spending). However, it adds nothing about unit/currency consistency, whether inflow and outflow are gross or net, or what an outflow of 0 means, 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?

The description names a specific verb ('Estimate') and resource ('months of runway') and enumerates the three driving inputs (cash balance, monthly income, monthly spending), which is enough to distinguish it from unrelated sibling calculators like break-even or LTV/CAC tools. It stops short of explicitly contrasting itself with the nearest financial siblings, so it lands at clear-but-not-differentiated.

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?

Usage context is only implied: 'constant monthly income and spending' signals this is a simple steady-state projection rather than a scenario or growth model, but there is no explicit when-to-use/when-not guidance or reference to an alternative tool for non-constant or growing cash flows. The agent must infer the boundary itself.

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.