Skip to main content
Glama

Save this session

save_session

Save a structured summary of completed work, decisions, and open tasks to resume the next session without starting over.

Instructions

Saves a structured summary of the current session so the next session can resume without re-asking. Use at the end of every meaningful session -- even if the user doesn't ask: 'summary', 'wrap-up', 'end of session', 'recap', 'we're done', 'see you next time', 'close out', or whenever significant work was completed, decisions were made, or open loops exist that need carrying forward. Also trigger at natural checkpoints mid-session when a major phase completes. Include: what was accomplished, key decisions made, open loops or next steps. Do NOT trigger after trivial exchanges (single Q&A, quick lookups) with nothing worth carrying forward. Do NOT trigger if the session has already been saved with no new work done since.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesUnique session identifier (timestamp or UUID)
summaryYesNarrative of what happened: decisions, work completed, problems solved
topicsNoTopic tags for searchability
open_loopsNoUnfinished tasks or questions to carry forward
decisionsNoKey decisions made during the session
platformNoPlatform this session ran onclaude-code
duration_minutesNoApproximate session duration
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only describes what to include, not whether saves overwrite, require permissions, or return values. No mention of side effects or safety considerations.

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?

Well-structured with front-loaded purpose, detailed usage triggers, and clear exclusions. Slightly verbose but each sentence adds value for the agent's decision-making.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema or annotations; the description should cover return values and error handling. It only covers usage context, missing behavioral details like return format or idempotency.

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% with good parameter descriptions. The description adds minimal extra meaning (e.g., suggesting content types) but does not provide examples or formats beyond the 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 saves a structured summary of the current session for resumption, with a specific verb ('saves') and resource ('structured summary of the current session'). It implicitly differentiates from sibling tools like 'save_conversation_turn' by focusing on session-level summaries.

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

Usage Guidelines5/5

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

Extensive when-to-use guidance is provided, including trigger phrases, mid-session checkpoints, and explicit exclusions for trivial exchanges. This tells the agent exactly when to invoke the tool.

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/malamutemayhem/unclick'

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