Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Deal Flow

Investors: list the startup pitches saved to your PitchSpark watchlist

pitchspark_list_watchlist_v1
Read-onlyIdempotent

List the pitches the investor has saved on PitchSpark (in the app or with pitchspark_watch_pitch_v1), newest first: id, company name, stage, sector, when saved and the link. Use when: the investor asks what is on their watchlist or saved pitches. Do not use for: saving (pitchspark_watch_pitch_v1), searching. Requires a PitchSpark API key from an investor account (self-declared; PitchSpark does not verify accreditation). Pitches that are no longer public or whose founders opted out of AI agents are left out and counted in unavailable_count. Up to 50 items. Uses none of the daily pitch allowance. Read-only. Calls are logged.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint=false), it discloses what an agent could not otherwise know: the API key and self-declared (unverified) accreditation, that non-public or opted-out pitches are omitted and surfaced via unavailable_count, the 50-item cap, that no daily pitch allowance is consumed, and that calls are logged. The 'Read-only' statement is consistent with readOnlyHint=true rather than contradicting it.

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 fields, then when/do-not-use, then constraints — the ordering an agent needs. Sentences are dense but each carries distinct information (purpose, routing, auth, exclusions, quota, logging); nothing is redundant padding.

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?

An output schema exists, so return-value documentation is unnecessary, and the description still covers everything else needed to call correctly: auth prerequisites, result-set exclusions with the unavailable_count signal, the size cap, and quota/logging side effects. For a simple read-only single-parameter list tool, nothing material is missing.

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 description coverage is 0% for the single `limit` parameter, so the description has to compensate; 'Up to 50 items' conveys the cap that explains the schema's default/maximum of 50. It stops short of saying the limit is caller-adjustable downward or naming the parameter, leaving a small gap, but the practical semantics (bounded result set) are communicated.

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?

Opens with a specific verb+resource ('List the pitches the investor has saved on PitchSpark') and enumerates the returned fields (id, company name, stage, sector, saved date, link). It explicitly contrasts with the sibling that creates the state it lists ('in the app or with pitchspark_watch_pitch_v1'), so an agent can distinguish it from pitchspark_watch_pitch_v1 and the search/list siblings 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?

Gives an explicit trigger ('Use when: the investor asks what is on their watchlist or saved pitches') and an explicit exclusion ('Do not use for: saving (pitchspark_watch_pitch_v1), searching'), naming the alternative for the saving case. When-to-use, when-not-to-use, and the routing target are all stated rather than inferred.

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