Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Deal Flow

List the startup searches saved under your API key

pitchspark_list_saved_searches_v1
Read-onlyIdempotent

List the searches saved with pitchspark_save_search_v1 under the caller's API key, newest first, each with the exact arguments to re-run it ("rerun": tool pitchspark_search_pitches_v2 and its arguments). Use when: the investor asks for their saved searches. Do not use for: running them (pass rerun.arguments to pitchspark_search_pitches_v2). Requires a PitchSpark API key (psk_...). Searches are per key, not per account. Read-only; uses none of the daily pitch allowance.

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_list_saved_searches_v1"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed (isError true).
itemsNo
max_per_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/destructive and closed-world, so the bar is lower; the description still adds real context: API key requirement (psk_...), per-key rather than per-account scoping, newest-first ordering, and the fact that it consumes none of the daily pitch allowance. The only gap is that it doesn't say what an empty result set looks like, though the output schema presumably covers that.

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

Conciseness5/5

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

Front-loaded with the action and return shape, then the when/do-not-use routing, then the preconditions and quota note. Every sentence carries distinct information — the key-per-account caveat and the allowance note both change caller behavior — and there is no filler.

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 zero-arg, read-only list tool with an output schema present, the description covers everything an agent needs: prerequisites, scoping model, ordering, quota impact, and the follow-up action for the returned payload. No return-value documentation is needed since the output schema exists.

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?

The tool takes zero parameters, so there is no parameter semantics to explain beyond noting that no filtering arguments exist (which is implicit in the API-key scoping statement). Baseline for a 0-param tool applies; nothing misleading is added.

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?

Names a specific verb and resource (list saved searches), states the scope (under the caller's API key, newest first) and the returned payload shape (each entry carries a "rerun" tool + arguments). It also names the sibling that creates these records (pitchspark_save_search_v1), so the agent can place it in the workflow without opening any 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?

Explicitly provides both directions: "Use when: the investor asks for their saved searches" and "Do not use for: running them (pass rerun.arguments to pitchspark_search_pitches_v2)". The alternative path is named along with the exact handoff data, leaving nothing 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