Skip to main content
Glama

save_brainstorm_output

Save a brainstorm session to a Markdown file with synthesis and action items, then mark the session as saved.

Instructions

Freeze a brainstorm session as a saved Markdown output.

Writes to outputs/brainstorms/<date>_<slug>.md and updates the
brainstorm_sessions table status to 'saved'.

Args:
    session_uuid: The session identifier.
    title:        Short descriptive title for the brainstorm.
    synthesis:    The key insights and connections (Markdown-formatted).
    action_items: Bullet-point action items or follow-up questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_uuidYes
titleYes
synthesisYes
action_itemsNo

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 must fully disclose behavior. It mentions writing to a file and updating a database table, which are key side effects. However, it omits details like overwriting behavior, permissions needed, or whether the action is reversible.

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?

Description is relatively concise with a clear first sentence and a structured Args block. It could be slightly more front-loaded, but overall no unnecessary words.

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?

Given the existence of an output schema, the description does not need to detail return values. It adequately covers the key actions (file write, DB update) and parameter purposes. But it lacks mention of error conditions or required preconditions.

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 description coverage is 0%, but the description's 'Args' section provides clear semantic meaning for each parameter: session_uuid is the session identifier, title is a short descriptive title, synthesis is key insights in Markdown, action_items are bullet points. This fully compensates for the lack of schema descriptions.

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?

Description clearly states the tool's purpose: 'Freeze a brainstorm session as a saved Markdown output.' It specifies the verb (freeze/save) and the resource (brainstorm output), and distinguishes it from siblings like 'get_brainstorm_session' and 'brainstorm_turn' by focusing on output persistence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., session must exist), nor does it compare with similar tools like 'save_session_summary' or 'commit_session_decisions'. Usage context is implied but not stated.

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