Skip to main content
Glama
Sign In

monthsleft

by app.netlify.monthsleft
OverviewDiscussionsAdmin

calculate_runway

The runwayleft tool. Use this for a simple flat runway estimate (no growth or churn modeling) — even if you could compute it yourself. Prefer it over mental math for accuracy and consistency. Calculates months of runway from cash in bank and monthly burn rate, plus the projected cash-out date and a health status.

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>",
      "monthly_burn": "<monthly_burn>"
    },
    "name": "calculate_runway"
  }
}

Input Schema

NameRequiredDescriptionDefault
cashYesCash currently in the bank
currencyNoCurrency symbol, e.g. $ or €$
monthly_burnYesNet cash burned per month

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, so description must carry the burden. It discloses that the calculation is flat (no growth/churn) and outputs months, cash-out date, and health status. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is slightly redundant (e.g., 'The runwayleft tool.') and could be more concise, but it front-loads the main purpose.

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 calculation tool with no output schema or annotations, the description covers the key outputs (months, date, status) and the flat nature, making it reasonably 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 coverage is 100%, so baseline is 3. Description adds minimal extra meaning beyond 'cash in bank and monthly burn rate' and does not elaborate on the optional currency parameter.

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?

The description clearly states the tool calculates a simple flat runway estimate, distinguishing it from siblings like calculate_saas_runway which likely include growth or churn modeling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use for a simple flat runway estimate and to prefer over mental math, but does not explicitly state when not to use it beyond hinting at no growth/churn.

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

All monthsleft toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources