Skip to main content
Glama

brainstorm_turn

Run a brainstorm session turn to retrieve relevant context, ideas, and library notes, guided by a steering mode (expand, focus, challenge, synthesize, connect).

Instructions

Run one turn of a brainstorm session, returning relevant context.

Call this at the start of a brainstorm and after each steering action.
The tool fetches relevant ideas, notes, questions, and library notes so
you (the AI) can surface connections the user may not have considered.

Steering modes:
  expand    — broaden; surface tangential connections
  focus     — narrow; find the most relevant threads
  challenge — find counter-arguments and weaknesses
  synthesize — identify themes; propose a unifying framework
  connect   — explicit cross-domain connections to library/literature

Args:
    topic:        The brainstorm topic or question.
    steering:     One of expand|focus|challenge|synthesize|connect.
    session_uuid: Pass the UUID from the previous turn to continue a session.
                  Omit to start a new session.
    turn_notes:   Optional free-text notes from the previous turn to log.

Returns JSON with: session_uuid, turn_number, context (ideas/notes/
questions/library), steering_prompts, and instructions for the AI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYes
steeringNoexpand
session_uuidNo
turn_notesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It describes the return format and steering behavior, but doesn't disclose side effects like session mutation, auth requirements, or rate limits. Adequate but not exhaustive.

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

Conciseness5/5

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

Well-structured with purpose, usage, steering modes, then args. Front-loads the key action and context. Every sentence delivers necessary information without fluff.

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 4-parameter tool with an output schema, the description covers all essential aspects: what, when, how, steering options, parameter details, and return fields. No gaps for typical use.

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

Parameters5/5

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

Schema has 0% description coverage, but the description's 'Args' section fully explains each parameter's purpose, steering values, session continuation, and optional notes. Completely compensates for the schema gap.

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?

Description clearly states 'Run one turn of a brainstorm session' and explains steering modes. It doesn't explicitly differentiate from sibling brainstorming tools like get_brainstorm_session or assemble_brainstorm_context, but the single-turn focus is clear.

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 says 'Call this at the start of a brainstorm and after each steering action', and describes each steering mode's purpose. Lacks explicit when-not-to-use or alternative tool names, but provides strong situational guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis_PH'

If you have feedback or need assistance with the MCP directory API, please join our Discord server