Skip to main content
Glama

founder_unit_economics

Compute deterministic unit economics, 12-month forecasts, break-even points, cash requirements, and sensitivity scenarios from fully specified financial assumptions to evaluate startup viability.

Instructions

Compute deterministic unit economics, 12-month forecast, break-even, cash requirement and sensitivity scenarios. Requires fully specified financial assumptions; never invent inputs.

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": {
      "financials": "<financials>"
    },
    "name": "founder_unit_economics"
  }
}

Input Schema

NameRequiredDescriptionDefault
financialsYesFinancial inputs according to references/number-schema.md. Example in examples/numbers.json.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the computation is deterministic and names the full set of results produced, but says nothing about what happens with incomplete or invalid input, whether anything is persisted, or how errors are surfaced.

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?

Two sentences, both front-loaded with the highest-value information: first what is computed, then the input constraint that governs whether the call is valid. No filler or redundant 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?

There is no output schema, but the description compensates by enumerating precisely what the tool returns. It also flags the qualification requirement for a nested-structure input. The only gap is behavior on underspecified financials, which is implied but not spelled out.

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% and the single parameter already points to references/number-schema.md and examples/numbers.json, so the baseline is 3. The description adds one meaningful constraint beyond the schema — that every assumption must be supplied rather than defaulted or invented — but gives no field-level detail for the nested financials object.

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 gives a specific verb ('Compute') plus a concrete resource and enumerates the concrete outputs: unit economics, 12-month forecast, break-even, cash requirement, and sensitivity scenarios. That is far more informative than the bare name, though it never explicitly names or contrasts the sibling tools, so it stops short of a 5.

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?

It states a clear precondition for invocation: financial assumptions must be fully specified, and the agent must never invent inputs. That is real guidance about when the tool is ready to be called. No exclusions or named alternatives are given, which keeps it out of 5 territory.

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