Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Deal Flow

What signed-in PitchSpark users decided about a startup pitch: anonymised pass reasons, ratings and engagement

pitchspark_get_decision_summary_v1
Read-onlyIdempotent

Summarise how signed-in PitchSpark users (not only investors) responded to one pitch: positive (likes and superlikes) vs passes (the thumbs block, currently withheld pending review: reason hidden_pending_review), the rating distribution and average (out of 10, to the nearest 0.5), the top pass reasons and "why we passed" themes (the team-related reasons and the team theme are withheld pending review and never listed; shares are over the listed reasons), time spent, and which pitch sections and score dimensions users read. Use when: an investor (or a founder's assistant) wants the crowd signal behind a pitch before deciding. Prefer it over pitchspark_get_pitch_v2 when only decision data is needed. Do not use for: who passed or liked (never returned), investor comments (never returned), the AI score (pitchspark_get_score_v1). Decision data from signed-in PitchSpark users needs a PitchSpark API key from an investor account (self-declared; PitchSpark does not verify accreditation): without one every decision block is available false with reason key_required. It is anonymised: counts of distinct people only, as bands ("5-9", "10-24", "25-49", "50+"), never who; shares and rates to the nearest 0.05; the pitch's founders, team and PitchSpark staff are never counted; guest and anonymous viewers are never counted; every block is withheld (reason below_min_k) when fewer than 5 distinct people are behind it, and a split (positive vs pass, rating bands) is withheld when any part of it would be under 5; no investor comment text is ever returned. Who is counted: ratings, reading time, sections and score views count ANY signed-in non-owner user (the writers check no account type), and likes, passes and pass reasons count signed-in users who swiped or gave pass feedback (also not restricted to investor accounts); only the caller of this tool must hold an investor key. Some fields are withheld pending a review (reason hidden_pending_review, or absent from a list): the team-related pass reasons and the pass rate (the likes-vs-passes thumbs block, the search card signal, investors_considered and the card-dwell figures). Treat a withheld field as no signal. Sources: signed-in users' swipe decisions (likes, passes, pass reasons, card dwell), structured pass feedback (never comment text), ratings, time on the pitch page and per-section dwell, and score-dimension views. A block with no source data is available false, reason no_data. Returns {"pitch_id","company_name","decisions":{min_k, investors_considered, truncated, thumbs, rating, pass_reasons, pass_themes, time_spent, sections, score_dimension_interest},"attribution"}. Without an investor API key the call still answers (and counts against the allowance like pitchspark_get_pitch_v1), but every block is withheld. 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_decision_summary_v1"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed (isError true).
pitch_idNo
decisionsNoAnonymised decision aggregates by signed-in PitchSpark users (not only investors); readable with investor API keys only (every block reason key_required otherwise). Counts are bands ("5-9", "10-24", "25-49", "50+"); every block is withheld below min_k distinct signed-in users (the counts cover any signed-in non-owner user, not only investor accounts).
attributionNo
company_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnly/idempotent annotations it discloses auth requirements (investor API key, self-declared, unverified accreditation), the failure mode when the key is absent (blocks available=false with reason key_required), the minimum-k suppression rule, anonymisation bands and rounding, exclusion of founders/team/staff/guests, and allowance accounting including the same-day 0-cost case and view logging. This is substantially more than the annotations carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and ordered sensibly, but the text is a dense wall with heavy redundancy: 'never comment text' is asserted three times, and the hidden_pending_review withholding is stated once inline and then re-stated in a later 'Some fields are withheld' paragraph. The parenthetical listing the pass-rate withholdings (thumbs block, search card signal, investors_considered, card-dwell figures) is garbled enough to obscure rather than clarify.

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 this is a read-only, single-parameter tool with an output schema, the description covers the essentials an agent needs: auth prerequisites, suppression reasons, what is never returned, and the response shape. The only shortfall is that the overlapping withholding passages leave the exact set of unavailable fields slightly ambiguous.

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?

There is a single required parameter whose schema description coverage is 100% ('The pitch id from a search result'). The prose adds nothing about the id's format or sourcing beyond what the schema already states, so the baseline of 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?

The opening sentence names a specific verb and resource — summarising how signed-in PitchSpark users responded to one pitch — and immediately enumerates the content (positives vs passes, rating distribution, pass reasons/themes, time spent, sections and score dimensions). It also explicitly distinguishes itself from pitchspark_get_pitch_v2 and pitchspark_get_score_v1, so an agent can route without opening sibling schemas.

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?

It gives an explicit 'Use when' condition (an investor or a founder's assistant wants the crowd signal behind a pitch), a stated preference over pitchspark_get_pitch_v2 when only decision data is needed, and a 'Do not use for' list that names who-passed, comments, and the AI score with the sibling that covers the latter. Both positive and negative selection guidance are present.

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