Skip to main content
Glama

browse_public_gallery

Search the Vouch public gallery of validated ideas that founders have chosen to share. Returns idea name, one-line description, target customer, and a link. Use when a user wants real examples of validated ideas, or to see how other founders framed a similar problem.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax ideas to return (default 10).
queryNoKeyword to filter idea names / target customer. Empty = latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does meaningful work: it reveals that results are limited to ideas founders opted to share (so absence of an idea is not evidence it doesn't exist) and it enumerates the return payload even though no output schema exists. It omits ordering, pagination, and result-count behavior, which is why it is not a 5.

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 tight sentences: purpose, return shape, then when-to-use. Nothing is repeated and the most important information leads.

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 simple two-parameter read tool with no output schema, the description supplies the essential missing piece by listing returned fields. Pagination and ordering semantics remain unspecified, but nothing critical to invoking it correctly is absent.

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 description coverage is 100%, so both limit (default 10, max 25) and query (keyword filter, empty = latest) are already documented. The description adds no additional parameter meaning, so the baseline 3 applies.

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 gives a specific verb ('Search') and a precisely scoped resource ('the Vouch public gallery of validated ideas that founders have chosen to share'), then names the returned fields. That scope language makes it unmistakably distinct from get_methodology, start_validation, or list_industry_templates without needing to name them.

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

Usage Guidelines4/5

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

It states a clear triggering condition: use when a user wants real examples of validated ideas or wants to see how other founders framed a similar problem. It stops short of exclusions, e.g. it never says what to use instead when the user wants the validation process itself rather than examples.

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