Skip to main content
Glama

Somebody Build This

Get an idea's builder brief

get_brief
Read-onlyIdempotent

Get one idea from Somebody Build This: the poster's own words, then a builder brief (a suggested weekend plan written by the site's AI steward, not by the person who posted the idea), a prompt for an AI coding tool, and how to ship. Pass the idea's slug (the last part of its URL, like "42-scale-reader") or its ticket number (like 42 or "#0042"). Ideas never lock; when it works, ship it by pressing "Ship it" on the idea page and pasting the link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe idea's slug ("42-scale-reader") or ticket number (42 or "#0042").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 the safety profile is covered. The description earns credit for going beyond that: it discloses that the brief is authored by the site's AI steward rather than the poster (a provenance/trust signal an agent needs when summarizing), that ideas "never lock" (no exclusivity or stale-state concerns), and that shipping is a manual page action, not a tool capability.

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?

Purpose and return contents are front-loaded in the first clause, so an agent gets the gist immediately. The single long sentence with nested parentheticals is denser than necessary, and the trailing shipping instructions are slightly tangential, though they usefully prevent an agent from attempting to ship via the tool.

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 one-parameter read tool with full annotation coverage and no output schema, the description is close to self-sufficient: it describes the payload shape, clarifies authorship of the brief, and notes that shipping happens outside the tool. The only gap is missing error behavior for invalid or unknown slugs/tickets.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds a small but real derivation hint beyond the schema by explaining the slug is "the last part of its URL." It also restates that both slug and ticket forms are acceptable, which the schema already conveys, so the added value is modest rather than substantial.

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 opens with a specific verb and resource ("Get one idea") and then enumerates exactly what comes back: the poster's own words, an AI-written builder brief, a coding-tool prompt, and shipping guidance. The singular "one idea" scopes it distinctly from a listing tool, and the unusual domain (Somebody Build This) is explained rather than assumed.

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?

Usage is only implied: you call this when you have a slug or ticket number and want the full brief for a single idea. There is no explicit statement of when to prefer this over the sibling listing tool, and no stated preconditions or failure conditions (e.g., what happens for an unknown slug).

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