get_brainstorm_sessionRetrieve all turns from a stored brainstorm session using its session UUID. Use this to review past ideas or resume the conversation.
Retrieve all turns in a brainstorm session.
Args:
session_uuid: The session identifier returned by brainstorm_turn().
| Name | Required | Description | Default |
|---|---|---|---|
| session_uuid | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description relies on 'Retrieve' to imply read-only behavior. It does not disclose any side effects, idempotency, or failure conditions, which is minimal for a retrieval tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with two sentences, including a structured args section. Every sentence serves a purpose with no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, output schema exists), the description sufficiently covers retrieval and parameter purpose. No additional content needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, but the description explicitly explains 'session_uuid' as 'The session identifier returned by brainstorm_turn()', adding source context beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Retrieve' and resource 'all turns in a brainstorm session', clearly distinguishing it from siblings like 'brainstorm_turn' which creates turns, and 'list_brainstorm_sessions' which lists sessions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as 'brainstorm_turn' or 'list_brainstorm_sessions'. The description lacks context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.