Skip to main content
Glama

Start a live brainstorm

start_brainstorm
Read-only

Get the link to a free live brainstorm: the host writes a question and shows a code on a screen; everyone adds ideas from their phone, anonymously; AI groups the ideas into themes; everyone votes with 3 dots; the results can be emailed to the host. Works in a room or on a video call.

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

Input Schema

NameRequiredDescriptionDefault
languageNoen, fr, de or es; default en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 is consistent with that by framing the action as 'get the link' rather than a stateful write. It adds genuine context beyond the annotations: no auth/account implied, anonymous participation, an auto-generated code, and an email-results option — useful for setting user expectations.

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 lead clause is well front-loaded, but the rest is a single semicolon chain mixing invocation-relevant facts with product mechanics ('3 dots', 'AI groups the ideas into themes') that do little to help an agent select or call the tool. It is readable but not efficiently prioritized.

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 zero-required-parameter tool with no output schema, the description covers the return value (a link), the free/anonymous nature, and both in-room and remote usage. What an agent needs to invoke it correctly is essentially all present; only sibling routing is missing.

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% and the single optional 'language' parameter is fully documented in the schema with its enum and default, so the description carries no extra burden. It adds nothing about the parameter, which is the expected baseline here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 deliverable: 'Get the link to a free live brainstorm', which tells an agent exactly what calling it produces. It does not name or contrast against the sibling 'start_' tools (start_360, start_johari), so differentiation must be inferred from the title alone.

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?

'Works in a room or on a video call' communicates the applicable context, and 'free' signals it is a lightweight/public offering. However, there is no explicit when-to-use vs. when-not guidance and no reference to the other start_* tools, leaving selection between siblings 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