Skip to main content
Glama
cachly-dev

cachly — AI Cognitive Brain

session_handoff

Save session progress, completed and remaining tasks, file changes, and instructions for the next chat window to ensure context continuity and prevent incomplete work.

Instructions

Save a detailed handoff for the NEXT chat window / session. Stores: current progress, TODO list (done + remaining), changed files with descriptions, instructions for the next assistant, and any incomplete work. The next session_start automatically includes this handoff so the new window knows EXACTLY what happened and what remains. Call this BEFORE closing a chat window, especially if work is incomplete. This prevents the "continue" problem where new windows lose context, skip tasks, or produce broken code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYesUUID of the cache instance
completed_tasksYesTasks that were fully completed (e.g. "Implemented brainSearch() in JS SDK")
remaining_tasksYesTasks NOT yet done — the next window MUST pick these up
files_changedNoChanged files with their current state — marks partial/broken files so next window knows to fix them
instructionsNoFree-form instructions for the next assistant. Be specific: what to do next, what to avoid, what broke.
context_summaryNoBrief summary of what happened this session (architecture decisions, key findings, blockers)
blocked_onNoIf work is blocked, describe what is needed to unblock (e.g. "waiting for API deploy", "needs user input on design")
Behavior4/5

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

The description discloses that the handoff is stored and automatically included in the next session_start. It does not mention potential side effects like overwriting previous handoffs or limitations, but given no annotations, it covers essential behavioral aspects adequately.

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, with the main purpose front-loaded. Every sentence adds value without redundancy, making it easy for an agent to quickly understand when and why to use the tool.

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 no output schema and 100% schema coverage, the description provides all necessary context: what the tool does, what it stores, when to call it, and how it integrates with session_start. It is complete for a write tool serving context transfer.

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%, so the description does not add new parameter details beyond what the schema already provides. The schema descriptions are sufficiently detailed, and the tool description reinforces their purpose, meeting the baseline expectation.

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 that the tool saves a detailed handoff for the next session, including progress, TODO list, changed files, instructions, etc. It distinguishes from siblings by specifying it is called before closing a chat window, especially when work is incomplete.

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?

The description explicitly tells when to use the tool: 'Call this BEFORE closing a chat window, especially if work is incomplete.' It explains the consequence of not using it, preventing the 'continue' problem, and implies the tool is for context transfer between sessions.

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/cachly-dev/cachly-mcp'

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