Skip to main content
Glama

Somebody Build This

List open ideas

list_open_ideas
Read-onlyIdempotent

List open ideas on Somebody Build This, a free public board where anyone posts something they wish existed and builders make it. Each idea has a ticket number, title, link, a one-sentence goal for a first weekend version, tags, and how many builds are in progress and shipped. Newest first. Ideas never lock: anyone can build any idea, even one someone else is building. Builders ship by pressing "Ship it" on the idea's page and pasting a link. Use get_brief for one idea's full text and suggested plan.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly ideas with this tag, like "home" or "for-kids".
limitNoHow many ideas to return (default 20, at most 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely useful behavior: results are newest-first and ideas are never locked, so concurrent builds are expected. However, the 'Ship it' instructions describe a workflow this read tool cannot perform and do not disclose anything about the read operation itself.

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

Conciseness3/5

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

The opening sentence is front-loaded and the get_brief routing is well placed at the end. But the middle sentences about how builders ship ('pressing Ship it and pasting a link') are promotional context that does not help an agent decide to call or how to call, so the description carries avoidable weight.

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?

There is no output schema, so enumerating the fields of an idea (ticket number, title, link, goal, tags, build counts) and the sort order is valuable and makes the return shape predictable. With only two optional, fully documented parameters, the remaining gap is minor.

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 100%, so both parameters (tag, limit) are fully documented in the schema, and the description adds no syntax or semantics beyond that. Baseline 3 applies when the schema carries parameter meaning.

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 resource ('List open ideas on Somebody Build This') and immediately defines what an idea is in this domain. It also explicitly separates itself from the sibling get_brief, so an agent can distinguish the list operation from the single-item fetch without opening either 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?

Explicitly routes single-idea lookups to get_brief ('Use get_brief for one idea's full text and suggested plan'), which is clear alternative guidance. It stops short of stating exclusions for this tool itself (e.g., that there is no search or status filter), so it is strong but not fully exhaustive.

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