Skip to main content
Glama
wdi-decision-intelligence

wdi-decision-intelligence

calculate_runway

Read-only

Compute months of cash runway after quitting, a pay cut, relocation, or career break, and see how long until your safety floor is reached.

Instructions

Compute months of cash runway after a change (quitting, pay cut, relocation, career break) and how long until a safety floor is reached.

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": {
      "liquid_cash": "<liquid_cash>",
      "monthly_essential_costs": "<monthly_essential_costs>"
    },
    "name": "calculate_runway"
  }
}

Input Schema

NameRequiredDescriptionDefault
liquid_cashYesCash you can access without penalty
one_time_costsNoOne-time costs, e.g. moving, repaying a signing bonus
extra_monthly_costsNoNew monthly costs caused by the change, e.g. self-paid health insurance
safety_floor_monthsNoMonths of essential costs to keep untouched (default 6)
monthly_income_afterNoMonthly income after the change (default 0)
monthly_essential_costsYesEssential monthly costs (housing, food, insurance, debt minimums)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by revealing a second computed output (time to safety floor), but it does not disclose modeling assumptions — whether investment returns, income growth, or variable costs are considered — which matters for a financial projection an agent will present as a number.

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 that pairs the primary output with the secondary one and nothing else. No filler, no restatement of the tool name.

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?

With no output schema, the description does the necessary work of naming both returned quantities, and all six parameters are documented in the schema. It falls short only on the assumptions behind the computation and output units, which for a financial projection would be worth one more clause.

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 100%, so every parameter is already documented in the input schema with examples (moving costs, self-paid insurance, default 6-month floor). The description adds only scenario framing that helps map life changes to optional parameters, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Compute') and a specific resource ('months of cash runway'), plus a secondary output ('how long until a safety floor is reached'). The parenthetical scenarios (quitting, pay cut, relocation, career break) make the domain unambiguous and clearly separate it from the sibling tools (evidence grading, option comparison, checklists).

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 description implies context of use by listing life changes it applies to, which gives an agent a usable trigger. However, it never states when not to use it (e.g., for ongoing income planning) or names any alternative tool for related questions, so guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.