Skip to main content
Glama

Founder take-home at exit, by funding stage

founder_exit_take_home
Read-onlyIdempotent

Runs the Founder Ventures Dilution Calculator: what the founding team takes home from an exit if bootstrapped versus after each funding stage, using Carta median ownership. Optionally adds your own ownership.

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": {
      "exit_value": "<exit_value>"
    },
    "name": "founder_exit_take_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
exit_valueYesExit value in USD.
your_ownership_pctNoOptional: your current founding-team ownership in %.

Output Schema

NameRequiredDescriptionDefault
urlYes
stagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so safety is covered. The description adds genuine context beyond them: the calculation's methodology and data provenance (Carta median ownership) and the bootstrapped-versus-staged comparison axis, which tells the agent what the output represents. It stops short of noting assumptions or caveats in the medians.

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?

Two tight sentences with the comparison axis front-loaded and no filler. The opening 'Runs the Founder Ventures Dilution Calculator' slightly restates the title before getting to the substance, which keeps it just below a 5.

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?

A low-complexity two-parameter model with full schema coverage, rich annotations, and an output schema, so return values need no explanation. The description is sufficient for correct invocation; only the absence of any methodological caveat keeps it from a 5.

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 both parameters are already documented. The description only reinforces that your_ownership_pct is optional and additive to the default model, adding marginal meaning beyond the schema's own 'Optional' label; baseline 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 and a precise, unmistakable resource: founder take-home at exit, bootstrapped versus each funding stage, based on Carta median ownership. An agent can distinguish this modeling tool from the surrounding list/read and SaaS-valuation siblings without opening the schema.

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 framing (compare bootstrap vs. funded outcomes, optionally layer in your own ownership) but there is no explicit when-to-use statement, no prerequisite on exit_value, and no exclusion or named alternative such as estimate_saas_valuation.

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