Skip to main content
Glama
Sign In

Idea Launch

by io.idea-launch
OverviewDiscussionsAdmin

Draft the idea brief

idealaunch_draft_brief

Generate suggested brief fields for an idea: target customer, why they'd care, the current alternative, and the primary market.

Returns suggestions without saving. Nothing on the idea changes until brief fields are saved.

Returns: { ideaId, saved: false, suggestions: { targetCustomer, whyTheydCare, currentAlternative, primaryMarket, signupIncentive, notesToAvoid }, note }.

Consumes one of the idea's AI generation turns. Costs no Ad Run credit.

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": {
      "ideaId": "<ideaId>"
    },
    "name": "idealaunch_draft_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaIdYes
response_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: it consumes one of the idea's AI generation turns, costs no Ad Run credit, and mutates nothing until fields are saved. These are exactly the quota/side-effect facts an agent needs before calling a tool whose readOnlyHint is false, and none are derivable from the annotation block.

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?

Front-loaded with the core action, then a bolded non-persistence warning, then return shape and cost. Tight overall, with slight redundancy between 'Returns suggestions without saving' and the 'Returns: { saved: false }' block, but every line carries information.

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 compensates by spelling out the returned object fields and the cost/consumption model. The only real hole is parameter documentation, which is left entirely to a schema that provides no descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it says nothing about the two parameters. ideaId is inferable from context but its format/required nature is never stated, and the response_format enum (markdown/json) is entirely unaddressed.

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 ('Generate suggested brief fields for an idea') and enumerates the exact fields produced (target customer, why they'd care, current alternative, primary market). The 'without saving' clause separates it from idealaunch_update_idea_brief without needing to name it.

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?

'Returns suggestions without saving. Nothing on the idea changes until brief fields are saved' clearly signals this is the draft/preview step that precedes a save. It gives a clear usage context but never explicitly names the persistence alternative or states exclusions such as when drafting is unnecessary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Idea Launch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources