Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

Startup runway and dilution

startup_runway_dilution
Read-onlyIdempotent

Model early-stage startup cash runway calendar exhaustion date, Post-Money SAFE note conversion cap dilution, and Series A unallocated option pool shuffle waterfall.

Behavior: Deterministic, idempotent calculation with zero external side effects. Computes net burn = grossBurn - revenue; Runway months = cashOnHand / netBurn. Models post-money SAFE equity percentage = safeInvestment / postMoneyCap. Simulates Series A pre-money option pool expansion (diluting existing holders prior to lead investor entry) and calculates founder post-financing ownership percentage.

Usage Guidelines: Use for venture capital fundraising planning, startup cash runway tracking, and cap table dilution modeling. Do not use for discounted cash flow or IRR project appraisal; use npv_irr instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_of_dateYesCivil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
cashOnHandNoCurrent cash reserves in bank in USD ($). Must be positive.
postMoneyCapNoAgreed valuation cap on the Post-Money SAFEs in USD ($).
monthlyRevenueNoMonthly recurring revenue (MRR) or cash collections in USD ($/mo). Default is 15000.
safeInvestmentNoTotal capital raised via Post-Money SAFE notes in USD ($).
seriesAPreMoneyNoAgreed Series A pre-money company valuation in USD ($).
monthlyGrossBurnNoTotal monthly cash operating expenses in USD ($/mo). Must be positive.
seriesAInvestmentNoNew equity capital invested by Series A lead investors in USD ($).
optionPoolExpansionPercentNoRequired post-closing unallocated employee stock option pool percentage (e.g. 10 for 10%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / as_of_date
      Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.",
+  "example": "2026-09-26",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "as_of_date"
+]
  2. Changed8 schema fields changed
    • changedInput schema / properties / cashOnHand / description
      Previous value: -"Current cash in bank in USD ($)"New value: +"Current cash reserves in bank in USD ($). Must be positive."
    • changedInput schema / properties / monthlyGrossBurn / description
      Previous value: -"Monthly operating cash outflows ($/mo)"New value: +"Total monthly cash operating expenses in USD ($/mo). Must be positive."
    • changedInput schema / properties / monthlyRevenue / description
      Previous value: -"Monthly recurring revenue MRR ($/mo)"New value: +"Monthly recurring revenue (MRR) or cash collections in USD ($/mo). Default is 15000."
    • changedInput schema / properties / optionPoolExpansionPercent / description
      Previous value: -"Required unallocated post-close option pool %"New value: +"Required post-closing unallocated employee stock option pool percentage (e.g. 10 for 10%)."
    • changedInput schema / properties / postMoneyCap / description
      Previous value: -"Post-money valuation cap ($)"New value: +"Agreed valuation cap on the Post-Money SAFEs in USD ($)."
    • changedInput schema / properties / safeInvestment / description
      Previous value: -"Post-money SAFE investment amount ($)"New value: +"Total capital raised via Post-Money SAFE notes in USD ($)."
    • changedInput schema / properties / seriesAInvestment / description
      Previous value: -"Series A new lead investment amount ($)"New value: +"New equity capital invested by Series A lead investors in USD ($)."
    • changedInput schema / properties / seriesAPreMoney / description
      Previous value: -"Series A pre-money agreed valuation ($)"New value: +"Agreed Series A pre-money company valuation in USD ($)."
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing the exact calculation formulas (net burn = grossBurn - revenue, runway months = cashOnHand / netBurn, SAFE equity % = safeInvestment / postMoneyCap) and the deterministic, side-effect-free behavior, which aligns with readOnlyHint and idempotentHint. It fully explains what happens internally.

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?

The three-paragraph structure is efficient: the first paragraph lists core outputs, the second explains the math and safety, the third gives usage boundaries. Every sentence adds new information; no fluff or repetition. It is front-loaded with the purposes and then details the mechanics.

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?

Given the complexity (9 parameters, no output schema), the description is quite thorough: it covers purpose, formulas, usage, and even mentions the 'shuffle waterfall'. The only minor gap is that it does not explicitly describe the exact output format (e.g., whether it returns a single JSON object with multiple fields), but this is implied by the listed calculations. The description is still strong overall.

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

Parameters5/5

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

While the input schema provides descriptions for every parameter (100% coverage), the description adds crucial semantic context by explicitly connecting parameters through formulas (e.g., how cashOnHand and monthlyGrossBurn combine to yield runway). This helps the agent understand the relationships and intent behind each field, far beyond a bare listing.

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 opens with a precise list of three distinct calculations (runway exhaustion date, SAFE conversion dilution, and option pool shuffle waterfall), naming specific resources and formulas. It clearly distinguishes this tool from financial cousins like npv_irr, so an agent can immediately recognize its scope.

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

Usage Guidelines5/5

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

Explicitly states when to use it ('venture capital fundraising planning, startup cash runway tracking, and cap table dilution modeling') and when not to ('Do not use for discounted cash flow or IRR project appraisal'), and directs the agent to the correct sibling (npv_irr). This is textbook guidance.

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

All TrueCalci 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