Skip to main content
Glama

Run a feature ideas study

ideas_run

Search Reddit (the last year) and X (the last three months) for people talking about the problem this product solves, read the busiest threads' comments, read this site, and group what at least two different people ask for into features it could add, each with their posts as evidence. In the background, a few minutes; call ideas afterwards. Costs $0.90 from the balance, charged only when it returns. Not charged when fewer than 10 posts can be read. At most one a day. State the price and wait for a yes before every study.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: background execution taking a few minutes, a $0.90 charge from the balance, charged only on return, waived under ten readable posts, and a once-per-day limit. The annotations mark readOnlyHint=false and openWorldHint=true, which is consistent with a job that spends money against external sources, so there is no contradiction. The only gap is whether the result is a fixed feature list or free-form prose, which 'ideas' presumably covers.

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

Conciseness4/5

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

Every clause carries real information — sources, scope windows, evidence rule, cost, charge conditions, cadence, and the confirmation gate — with nothing to trim. The opening sentence, however, packs a whole pipeline into one long clause chain, so scanning takes more effort than a short bulleted breakdown would; front-loading the deliverable and cost separately would read cleaner.

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 no-input, no-output-schema, billed background job, the description covers what will be fetched, the evidence bar for inclusion, runtime expectations, billing conditions, rate limits, and the required user confirmation. An agent has enough to invoke it correctly and warn the user about cost and latency.

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 schema has zero parameters and 100% coverage, so there is no parameter meaning left for the description to add. Baseline of 4 applies; nothing about inputs needs clarifying.

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?

States a specific verb and deliverable (run a feature ideas study) and then spells out the mechanism: Reddit over the last year, X over the last three months, busiest-thread comments, this site, and grouping asks from at least two different people into features with their posts as evidence. It also names the sibling 'ideas' that returns the results, so an agent can distinguish it from adjacent tools.

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?

Explicit about sequencing ('call ideas afterwards'), about cadence ('at most one a day'), and about the pre-call gate ('state the price and wait for a yes before every study'). It tells the agent both what to do before invoking and what to do after, leaving little 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