Skip to main content
Glama

Wall of Decks

search_slides

Find slides from real pre-seed and seed pitch decks. Filter by section, stage, outcome and reviewer verdict, or search by company and slide text. Returns the slide image URL, its position in the deck and any reviewer comment.

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": "search_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoWords to match in the company name, slide title or review note.
stageNo"early" is pre-seed and angel rounds.
outcomeNo"failed" covers failed raises and rejected versions.
sectionNoA section id from list_sections, e.g. "team" or "ask".
verdictNoOnly slides a reviewer or the founder commented on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the return shape (image URL, deck position, reviewer comment) and the data provenance (real funded/failed pre-seed and seed decks). It omits safety/read-only framing, pagination behavior, and what the limit cap means, which matter for an iterative search tool.

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?

Three short sentences: what it searches, how to narrow, what comes back. No filler, and the core purpose is front-loaded.

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?

For a six-parameter, no-required-parameter search tool with no output schema, the description covers source scope, filter dimensions, and the returned fields. It stops short of explaining result ordering or how the default limit interacts with paging, but nothing essential to calling it is missing.

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 83%, so the schema already defines query, stage, outcome, section and verdict well, including enum meanings. The description restates the filter set and adds only the minor nuance that verdict filtering ties to reviewer/founder comments, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Find) and resource (slides) constrained to real pre-seed and seed pitch decks, and mentions both retrieval modes (filter and text search). It does not name a sibling such as get_deck or list_decks, so the boundary with those tools is left for the agent to infer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence 'Filter by section, stage, outcome and reviewer verdict, or search by company and slide text' indirectly tells an agent how to use the tool, and the verdict wording hints at when results are narrowed to commented slides. There is no explicit when-to-use versus get_deck/list_decks guidance or exclusions.

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