Skip to main content
Glama

Mode VC Chart: Ollama Downloads: Is Local LLM Adoption Keeping Up?

Cofounder Equity Split and ARR Multiple Calculator

calc_cofounder_equity
Read-onlyIdempotent

Splits founder equity from weighted contribution scores (product and IP 40%, distribution 35%, commitment 25%) after the option pool and Founder Institute FAST advisor grants, and applies a heuristic SaaS and AI-native ARR multiple. Same math as https://modevc.com/tools/cofounder-equity-valuation. The multiple is a rule of thumb from the web page, not a market valuation. Illustrative, not legal advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calc_cofounder_equity"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrNoARR in USD. Web default 1,200,000.
ndr_pctNoNet dollar retention in percent. Web default 122.
fast_tierNoAdvisor tier. Web default strategic.
cofoundersNoEach founder scored 0 to 100 on three axes. Omit to use the web calculator example of two founders.
fast_stageNoCompany stage for the FAST grant. Web default startup.
growth_pctNoYear over year growth in percent. Web default 140.
num_advisorsNoNumber of FAST advisors. Web default 2.
option_pool_pctNoEmployee option pool reserve, in percent. Web default 10.
gross_margin_pctNoGross margin in percent. Web default 76.

Output Schema

NameRequiredDescriptionDefault
as_ofNo
provenanceYes
source_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "provenance": {
      +      "properties": {
      +        "as_of": {
      +          "type": "string"
      +        },
      +        "as_of_basis": {
      +          "type": "string"
      +        },
      +        "sources": {
      +          "items": {
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "as_of",
      +        "as_of_basis",
      +        "sources"
      +      ],
      +      "type": "object"
      +    },
      +    "source_urls": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "provenance"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful context beyond that: the multiple is 'a rule of thumb from the web page, not a market valuation,' and the math is deterministic and matches a specific published calculator. It does not disclose the order of operations in enough detail to be considered rich behavioral disclosure, and with four annotations present a 3 is the right place.

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?

Three compact sentences, front-loaded with the mechanism and weights before the caveats. The URL reference earns its place by justifying the 'same math' claim, and nothing is repeated from the schema. Slight tightening of the final caveat sentence is possible, but there is no filler.

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?

Nine parameters are all optional with schema-documented defaults, and an output schema exists, so the description need not restate defaults or return shape. It covers the mechanism, the ordering constraint (pool and FAST grants first), and the interpretive limits of the multiple. It could have said what happens when cofounders is omitted (equals the two-founder web example) to round out behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline would be 3, but the description adds meaning the schema cannot: it states that the split happens AFTER the option pool and FAST advisor grants, which tells the agent the semantic ordering of option_pool_pct and the FAST parameters. The 40/35/25 weights also map each cofounder score field to its actual influence.

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 uses a specific verb+resource ('Splits founder equity') and states the exact inputs that drive the split (product/IP 40%, distribution 35%, commitment 25%), plus a second function (heuristic ARR multiple). It does not name or contrast any sibling calculator, so an agent must infer the difference from calc_saas_metrics or calc_safe_dilution on its own.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only boundary offered is the caveat 'Illustrative, not legal advice,' which limits reliance on the output but does not help an agent choose this tool over the many neighboring calculators.

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