Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Deal Flow

Search pre-seed and seed startup pitches by meaning

pitchspark_search_pitches_v3
Read-only

Find pre-seed and seed startups that are actively raising by what the investor means, not only the words used (e.g. "software that helps independent clinics get paid faster" finds revenue-cycle and payments pitches that never say "get paid"). Use when: an investor describes the kind of company they want in their own words (a problem, a customer, a business model) rather than exact keywords. Prefer it over pitchspark_search_pitches_v2 for descriptive queries; use pitchspark_search_pitches_v2 to sort by score, recency or views. Do not use for: reading one pitch in depth (pitchspark_get_pitch_v2), founder contact details, decks or data rooms (never returned), investment advice. The filters (sector, stage incl. "early", HQ region, raise range, minimum public score, traction, green flags, listed or updated within N days) narrow the list first; the query then ranks what is left. Ranking uses embeddings when they are available (similarity blended with the public score and recency) and falls back to the keyword + synonym ranker of pitchspark_search_pitches_v2 when they are not. Every reply states which in "search_mode" (semantic, mixed or keyword_fallback) with "fallback_reason". Returns the same lightweight cards as pitchspark_search_pitches_v2, "page" (cursor paging) and "coverage". Email addresses and phone numbers are removed from the query before it is used. 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. Errors are JSON {"error":{"code","message","category","retryable"}}: INVALID_ARGUMENT, UNAUTHORIZED, RATE_LIMITED, INTERNAL.

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": {
      "query": "<query>"
    },
    "name": "pitchspark_search_pitches_v3"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. A value above the caller's tier ceiling is reduced to it.
queryYesWhat the investor is looking for, in plain language, 1 to 500 characters. Ranked by meaning when semantic ranking is available, by keyword + synonym otherwise (search_mode says which).
stageNoFunding stage or list. "early" means pre_seed, seed and series_a.
cursorNopage.next_cursor from the previous call with the SAME query and filters.
sectorNoSector key or list of up to 10 (primary or additional sector). Keys: fintech, healthtech, saas, marketplace, ai_ml, consumer, enterprise, climate, edtech, crypto, biotech, hardware, gaming, real_estate, food_beverage, fashion, travel, sports, media, femtech, cybersecurity, dev_tools, ecommerce, logistics, mobility, hr_tech, legal_tech, insurtech, proptech, agtech, energy, robotics, govtech, hospitality, other.
locationNoHQ region key or list: us, canada, latam, uk, europe, mea, apac, global_remote.
min_scoreNoPublic PitchSpark score at least this (values under 70 are read as 70; pitches without a public score are left out).
green_flagsNoTraction signal: at least one of these founder-chosen green flags (e.g. "Profitable", "Signed LOI").
has_tractionNoTraction signal: true = only pitches with a public traction note.
max_raise_usdNoRaise at most this many US dollars (disclosed asks only).
min_raise_usdNoRaise at least this many US dollars (disclosed asks only).
created_within_daysNoRecency: listed on PitchSpark within this many days.
updated_within_daysNoRecency: pitch updated within this many days.

Output Schema

NameRequiredDescriptionDefault
pageNo
errorNoPresent only when the call failed (isError true).
pitchesNo
coverageNo
truncatedNo
attributionNo
search_modeNoHow this reply was ranked: semantic (by meaning), mixed (by meaning, then keyword matches among pitches without a current embedding) or keyword_fallback (keyword + synonym matching, as pitchspark_search_pitches_v2).
fallback_reasonNoWhy the reply is not fully semantic; null when search_mode is semantic.

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?

Goes well beyond the readOnly/openWorld annotations: it discloses that filters are applied before ranking, that ranking degrades to a keyword+synonym fallback and reports it in 'search_mode'/'fallback_reason', that PII is stripped from the query, that each returned pitch consumes the daily allowance (0 if already seen today via the same key or connection), and that calls are logged with views counted.

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?

Front-loaded with the purpose and example, then cleanly segmented into 'Use when', 'Prefer over', 'Do not use for', and mechanics. It is dense and slightly overlong — the error-code enumeration and 'same lightweight cards as v2' restate structured information — but nearly every sentence carries decision-relevant content.

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 13-parameter, open-world search tool with an output schema, it covers the ranking pipeline, fallback conditions, quota/allowance accounting, query sanitization, and paging cursor semantics. An agent has everything needed to choose it, call it correctly, and interpret degraded results.

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 coverage is 100%, so detailed per-parameter semantics are already handled, and the enum-like values ('early', region keys, sectors) are documented there. The description adds only the conceptual ordering (filters narrow, query ranks) and a high-level enumeration of filter categories, which is useful but marginal over 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?

Uses a specific verb and resource (find pre-seed and seed pitches by meaning) and immediately anchors it with a concrete example query. It also names the adjacent tools (pitchspark_search_pitches_v2, pitchspark_get_pitch_v2) so the agent can tell it apart without opening a schema.

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' condition (investor describes a problem, customer, or model in their own words), an explicit preference rule over v2 for descriptive queries, a rule for when v2 is better (sorting by score, recency, views), and a 'Do not use for' list naming alternatives and out-of-scope data.

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