Skip to main content
Glama

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.1/5.0
Behavior4/5

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

Goes meaningfully beyond the readOnly/openWorld/non-destructive annotations by disclosing data provenance (Carta State of Private Markets, quarterly) and a per-call price of $0.02 USDC, which is operationally important for an agent deciding whether to call. The gap is that it never says what happens when the optional `sector` is omitted, nor how coarse or current the returned figures are beyond 'quarterly'.

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?

Four short sentences, front-loaded with the resource and its metrics, then provenance, audience, and price. The audience sentence is the softest — it is closer to positioning than instruction — but it still conveys use-case signal, so little is wasted.

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 two-parameter lookup with no output schema, the definition covers what the tool is, what it returns conceptually, where the data comes from, and what it costs. The only material omission is the behavior of the optional `sector` parameter, which an agent would need to decide between a sector-specific and sector-wide call.

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 carries the full burden and only partially meets it: 'by stage and sector' tells the agent both parameters shape the result, but adds no meaning about the enum values, the fact that `stage` is required while `sector` is optional, or the default behavior when sector is absent. Enum values themselves are self-explanatory, which keeps this from dropping lower.

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 resource — venture capital round benchmarks — and enumerates the exact metrics returned (pre-money valuation, round size, dilution, option pool) plus the two dimensions that slice them (stage, sector). Against a catalog of ~30 sibling benchmark tools, the domain is unmistakable from the first sentence.

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?

Names the audience and the job to be done — 'founders, VC CFOs, and early-stage investors for round pricing and cap table modeling' — which gives an agent a concrete trigger. It stops short of explicit when-not guidance or naming an alternative for, say, public-market valuation comparisons, so it lands at 4 rather than 5.

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