Skip to main content
Glama

Check if a company is default alive

check_default_alive
Read-onlyIdempotent

Runs the Founder Ventures Default Alive Calculator: projects cash month by month from today's cash, revenue, growth and costs, and says whether the company reaches profit before the money runs out.

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_revenue": "<monthly_revenue>",
      "monthly_growth_pct": "<monthly_growth_pct>",
      "monthly_fixed_costs": "<monthly_fixed_costs>"
    },
    "name": "check_default_alive"
  }
}

Input Schema

NameRequiredDescriptionDefault
cashYesCash in the bank today, USD.
monthly_revenueYesRevenue this month, USD.
variable_cost_pctNoCosts that scale with revenue, in % of revenue. Default 0.
monthly_growth_pctYesMonthly revenue growth in %, for example 5.
monthly_fixed_costsYesFixed monthly costs today, USD.

Output Schema

NameRequiredDescriptionDefault
urlYes
verdictYes
breakeven_monthYes
out_of_cash_monthYes
current_monthly_burnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the bar is lower. The description adds real behavior: the projection is month-by-month starting from today's cash, and the result is a binary profit-before-cash-out verdict, telling the agent what the computation does. It stops short of disclosing model assumptions (e.g. no new funding, growth held constant) or the response shape.

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 well-formed sentence that names the calculator, summarizes the computation, and states the output verdict. The key noun is front-loaded and no wording is wasted.

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?

An output schema exists, so return values needn't be explained, and annotations carry the safety profile. What remains thin is disclosure of the projection's modelling assumptions, which materially affect the answer for a forecasting tool.

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% with units, defaults and examples documented per field, so baseline 3 applies. The description reinforces that inputs describe today's state ('from today's cash, revenue, growth and costs') but adds no syntax or edge-case detail, and never mentions variable_cost_pct.

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?

Specific verb and resource: runs the Founder Ventures Default Alive Calculator, projects cash month by month from today's cash, revenue, growth and costs, and reports whether profit is reached before cash runs out. That names both the methodology and the verdict, distinguishing it from valuation and exit-planning siblings.

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 is implied by the scenario (a company with cash, revenue, growth and costs asking whether it survives), but there is no explicit when-to-use statement or exclusion relative to siblings like estimate_saas_valuation or founder_exit_take_home. No prerequisites or caveats on which figures to supply are given.

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.

Resources