Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Deal Flow

Rank startup pitches against an investment thesis, with a fit rationale

pitchspark_thesis_fit_v1
Read-only

Rank PitchSpark pitches by how well they fit an investment thesis: either thesis text you pass, or the investor's saved thesis and preferences on PitchSpark (use_saved_thesis). Each result has a fit_score (0-100) and a rationale listing exactly which criteria matched. Use when: an investor asks "what fits my thesis". Prefer pitchspark_search_pitches_v2 for explicit filters. Do not use for: investment advice; the fit is a rule-based match, not a judgement. How it works (rule_based_v1, no model call): the thesis is read for sectors, stages, HQ regions and keywords (the same rules as search); a pitch earns points for each criterion it meets (sector 35, stage 25, region 10, keywords up to 30), scaled to the criteria the thesis names. Pitches that meet none are left out. Requires a PitchSpark API key (psk_...). The thesis text is never logged or stored. Returns {"pitches":[{card, fit_score, rationale}], "thesis", "method", "attribution"}. Up to 10 results (25 on a paid key). 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pitchspark_thesis_fit_v1"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
thesis_textNoThe thesis in plain English, 20 to 2000 characters. Not with use_saved_thesis.
use_saved_thesisNotrue: use the thesis and sector / stage / geography preferences saved on the key owner's PitchSpark profile. Not with thesis_text.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed (isError true).
methodNo
thesisNoThe structured thesis that was matched: sectors, stages, regions, keywords, source.
pitchesNo
truncatedNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent/destructive, but the description goes far further: no model call, exact scoring weights (sector 35, stage 25, region 10, keywords up to 30), zero-match pitches excluded, API key requirement, thesis never logged, calls logged, and each returned pitch consuming a daily allowance with a same-day dedupe exception. The non-idempotent hint is consistent with per-call counting, so no contradiction.

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 purpose, then when-to-use, then mechanism and cost. Dense but nearly every clause carries call-relevant information; the weighted-scoring parenthetical is the only part that verges on over-detailed for selection purposes.

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 3-parameter ranking tool with an output schema, the description still spells out return shape ({pitches:[card, fit_score, rationale], thesis, method, attribution}) and the constraint that some pitches may be omitted. Auth, quota, and privacy behavior are all disclosed, leaving nothing an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the description fills the remaining gap by explaining the result cap in business terms ('Up to 10 results (25 on a paid key)'), which the schema only encodes as default 10 / maximum 25. The mutual exclusivity of thesis_text and use_saved_thesis is stated in both places, and the saved-thesis source is clarified as the key owner's profile.

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 opens with a specific verb+resource+scope: rank pitches by fit to an investment thesis, with two sourcing modes (thesis_text vs use_saved_thesis). It explicitly distinguishes itself from pitchspark_search_pitches_v2 ('prefer ... for explicit filters') and rejects a nearby misread ('not investment advice; rule-based match').

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 trigger phrase ('what fits my thesis'), a named alternative for filter-driven queries, and a negative boundary (do not use for investment advice). Both when-to-use and when-not are covered.

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