Skip to main content
Glama

save_brainstorm_output

Save a brainstorm session's key insights and action items as a Markdown file, freezing the session for later reference.

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
Behavior4/5

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

With no annotations provided, the description bears full responsibility for behavioral transparency. It discloses that the tool writes to a specific file path and updates a database table status. While it does not cover error conditions or irreversibility, it provides sufficient context about side effects for a save operation.

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?

The description is concise and well-structured: a one-sentence purpose statement, followed by file/database details, then a clear parameter list. Every sentence adds value without redundancy.

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?

Given the simple nature of the tool and the presence of an output schema (not shown), the description covers all necessary aspects: what it does, what it creates/modifies, and what parameters are needed. It is complete for an agent to invoke correctly.

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 compensates fully by documenting all four parameters in the Args section. Each parameter gets a meaningful explanation (e.g., 'key insights and connections' for synthesis), adding significant value beyond the bare schema.

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?

The description clearly states the tool's purpose: to freeze a brainstorm session as a saved Markdown output. It specifies the verb (freeze/save) and the resource (brainstorm session output), and differentiates from siblings like 'brainstorm_turn' or 'assemble_brainstorm_context' by focusing on finalization and 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. The description only explains what the tool does, not when it should be preferred or if there are prerequisites. Siblings like 'brainstorm_turn' suggest iterative use, but no comparative advice is given.

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'

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