Skip to main content
Glama

Mode VC Chart: Anthropic SDK vs. OpenAI SDK: npm Downloads

Fundraising Readiness: Data Room Score, Runway and Burn Multiple

calc_fundraising_readiness
Read-onlyIdempotent

Scores diligence readiness from a weighted 12-item data room checklist (overall, Corporate and Legal, and each pillar), and computes runway and burn multiple from cash, burn and ARR growth. Same scoring as https://modevc.com/tools/fundraising-readiness. The investor-update email draft on that page is not included.

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_fundraising_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrNoARR in USD. Web default 780,000.
cashNoCash in the bank in USD. Web default 1,450,000.
raise_targetNoRaise target in USD (echoed, not used in the score). Web default 3,500,000.
mom_growth_pctNoMonth over month ARR growth in percent. Web default 18.
documents_readyNoChecklist items that are ready. Omit to use the web calculator example (all except valuation_409a, retention_cohorts, architecture_and_security). Pass [] for none.
monthly_net_burnNoMonthly net burn in USD. Web default 65,000.

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the scoring is deterministic and matches a published web calculator, and it explicitly states what is not included (the email draft). It does not discuss default-substitution behavior for omitted inputs, which the schema only partially covers.

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 sentences, front-loaded with the primary capability and followed by the scope exclusion. Dense but every clause carries information; the URL reference is the only mildly expendable element.

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 need not be explained, and the description covers inputs, scoring basis, and exclusions. The one gap is the relationship to the overlapping sibling tool, which matters for a calculator suite this large.

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%, so every parameter is already documented, including the web defaults and the documents_ready omission semantics. The description only restates the input categories (cash, burn, ARR growth) without adding format or interaction detail, so the baseline 3 applies.

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 names specific verbs and resources: scoring a weighted 12-item data room checklist (overall, Corporate and Legal, and each pillar) plus computing runway and burn multiple from cash, burn and ARR growth. That is far more than a restatement of the name. It stops short of 5 because the runway/burn-multiple half overlaps with the sibling calc_burn_multiple_runway, and the description never distinguishes the two.

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 (diligence readiness for a fundraise) and the description scopes out the investor-update email draft, which is a useful exclusion. However, there is no explicit when-to-use guidance and no routing to alternatives such as calc_burn_multiple_runway for pure runway math, leaving the agent to infer which tool to pick.

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