Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Deal Flow

Get a startup pitch's PitchSpark AI score, dimension scores and roast commentary

pitchspark_get_score_v1
Read-onlyIdempotent

Get PitchSpark's AI pitch score for one pitch: the composite (0-100), the six dimensions (market, problem, traction, moat, financials, team, each 0-100 with the model's analysis) and the Roast Room commentary when the pitch was roasted. Use when: an investor asks how PitchSpark rates a pitch, or where it is strong and weak. Prefer it over pitchspark_get_pitch_v2 when only the score is needed. Do not use for: scoring your own text (pitchspark_roast_text_v1, when enabled), what signed-in users decided (pitchspark_get_decision_summary_v1), investment advice. Limits of the data: scores are published only at 70 or above; below that pitchspark_score is null and the dimensions are withheld (dimensions_withheld "not_public"): null means no public score, not a low one. Dimensions and analyses need an API key (dimensions_withheld "key_required" without one). Roast text is filtered for personal attacks and contact details. Same access as pitchspark_get_pitch_v1: anonymous callers allowed under the daily allowance. Returns {"score":{pitch_id, company_name, pitchspark_score, scale, public_min, dimensions, dimensions_withheld, scoring_version, scored_at, roast}, "attribution"}. Each pitch this tool returns counts 1 against the daily pitch allowance (the same allowance as pitchspark_search_pitches_v1), or 0 when the same API key (without a key, the same connection) already got that pitch today. Calls are logged, and each pitch returned is counted as a view.

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": {
      "id": "<id>"
    },
    "name": "pitchspark_get_score_v1"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe pitch id from a search result ("id").

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed (isError true).
scoreNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent safety, but the description discloses far more: scores are published only at 70+, null pitchspark_score means 'not public' rather than low, dimensions are withheld as 'not_public' or 'key_required', roast text is filtered for personal attacks and contact details, anonymous access is allowed under a daily allowance, and each returned pitch costs 1 allowance (0 for repeats today) and counts as a view with logging.

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?

Purpose and usage lead, followed by data limits and cost – a sensible ordering for the agent's decision flow. It is dense and slightly redundant at the end, where allowance accounting and view/logging are restated in two consecutive sentences, and the return-shape listing duplicates the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-param read, the description covers everything the agent needs: when to call it, when not to, why a score may be null, when a key is required, what it costs against the daily allowance, and access level. Return-value explanation is partly duplicated by the output schema but the null semantics are essential context.

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?

With a single parameter at 100% schema coverage, the schema already defines id including its pattern and provenance. The description adds no further constraint or format guidance for id, so the baseline 3 applies.

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 verb and resource ('Get PitchSpark's AI pitch score for one pitch') and enumerates the payload: composite 0-100, six named dimensions with analysis, and Roast Room commentary. It also differentiates itself from pitchspark_get_pitch_v2 by saying it is preferred when only the score is needed.

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?

Explicit 'Use when' triggers (investor asks how PitchSpark rates a pitch, or where it is strong/weak), an explicit 'Do not use for' list naming three siblings (roast_text, decision_summary) plus investment advice, and a routing rule against pitchspark_get_pitch_v2. Nothing about selection is left to inference.

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