Skip to main content
Glama

Stratalize Intelligence

Get Venture Benchmark

get_venture_benchmark
Read-only

Venture capital round benchmarks — pre-money valuation, round size, dilution, and option pool standards by stage and sector. Source: Carta State of Private Markets quarterly. Used by founders, VC CFOs, and early-stage investors for round pricing and cap table modeling. $0.02 USDC per call.

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": {
      "stage": "<stage>"
    },
    "name": "get_venture_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageYes
sectorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, openWorldHint, and destructiveHint=false. The description adds useful context beyond annotations: data provenance (Carta State of Private Markets quarterly) and a per-call cost of $0.02 USDC, which is important for invocation decisions. It does not cover freshness limits, latency, or authentication, but it meaningfully improves transparency.

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 description is front-loaded with the core purpose and metrics, then adds source, audience, and price in compact form. Every sentence carries information relevant to selecting and invoking the tool, with no wasted wording.

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?

For a read-only benchmark retrieval tool with no output schema, the description covers the main metrics returned, data source, cadence, intended audience, and cost. It falls short only on optional parameter behavior and exact return structure, but it is sufficient for correct selection and invocation.

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 0%, so the description needs to compensate. It says the benchmarks are broken down 'by stage and sector,' which identifies both dimensions, but it does not state that stage is required, nor does it explain sector omission behavior or add meaning beyond the enum labels already visible in the schema.

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 states a specific verb and resource — venture capital round benchmarks — and lists the exact metrics covered: pre-money valuation, round size, dilution, and option pool standards. It clearly distinguishes this from the many unrelated benchmark siblings by naming the domain and the stage/sector dimensions.

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 gives clear usage context by naming the intended audience (founders, VC CFOs, early-stage investors) and use cases (round pricing and cap table modeling). It does not explicitly state exclusions or route to alternative tools, but the domain specificity makes sibling confusion unlikely.

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