Skip to main content
Glama

DECA Labs

Product ideas

get_ideas
Read-only

Consumer product ideas DECA's engine wrote from the demand signals and judged worth testing, best first, each with the apps and posts it rests on and its expected sign-up rate. Ideas another founder is testing are not shown. Pass id to read one idea. Free.

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

Input Schema

NameRequiredDescriptionDefault
idNoOne idea's id, to read only that idea. Optional.
limitNoHow many to return, 1 to 25. Default 10.
queryNoWords that must all appear in the idea. Optional.
verdictNoOnly ideas the judge rated this way. Optional.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description stays consistent while adding real context: result ordering ('best first'), item composition (apps and posts backing each idea), an expected sign-up rate field, an exclusion rule, and a cost note. It does not mention how the top-25 cap or truncation behaves, which keeps it from 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, front-loaded with what the tool returns and how results are ordered, followed by the exclusion and the id shortcut. No restated title, no filler.

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?

With no output schema, the description carries the burden of describing returned content and does so (apps, posts, expected sign-up rate, ranked order). It omits any statement about result volume or how far the ranked list extends beyond the limit cap, a minor gap for a zero-required-param read tool.

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 the schema already documents id, limit, query, and verdict. The description's only added meaning is that id yields a single idea in list form and that ordering is best-first, which is marginal beyond the schema baseline.

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 names a specific resource (consumer product ideas written by DECA's engine from demand signals and judged worth testing) and states the ordering (best first) and what each item contains. The exclusion rule 'Ideas another founder is testing are not shown' scopes it against sibling surfaces like get_my_ideas without the agent needing to open another schema.

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 gives a concrete usage condition — pass id to read a single idea — and clarifies scope with the founder-testing exclusion, plus 'Free' signals cost-free invocation. It stops short of explicitly naming the alternative tool to use when the agent wants its own ideas, leaving that routing 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