Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

session_handoff

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "completed_tasks": "<completed_tasks>",
      "remaining_tasks": "<remaining_tasks>"
    },
    "name": "session_handoff"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses what is stored and that the next session_start automatically consumes the handoff, which is useful context. However, it omits write semantics such as overwrite behavior, authentication needs, return/confirmation behavior, or rate limits.

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?

The definition is front-loaded with purpose and stored content, followed immediately by call timing. Every sentence is relevant, though the final 'continue problem' rationale is somewhat rhetorical. Overall it is concise and readable.

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?

For a 7-parameter write tool with full schema descriptions and no output schema, the definition covers purpose, timing, and downstream automatic use. It is nearly complete but leaves out return/overwrite behavior and annotation-level safety signals.

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 description coverage is 100%, so parameter documentation largely lives in the schema. The description groups stored content into progress, TODO done/remaining, changed files, instructions, and incomplete work, adding some conceptual framing. It adds no syntax, format, or default details 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 opens with a specific verb and resource ('Save a detailed handoff') and scopes it to the next chat window/session. It explicitly links the saved handoff to session_start, which differentiates it from session_start itself.

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

Usage Guidelines4/5

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

It explicitly says to call this before closing a chat window, especially when work is incomplete, giving a clear trigger condition. It does not state when not to use it or compare it with session_end or other alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.