SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_memory_handoff

Save task state at session end, posting handoff details to a crosslink channel and logging a milestone so the next session can resume with full context.

Instructions

Mutating: runs the session-end handoff protocol — three writes at once. task (required) names the work. status defaults to "in-progress" (also: blocked, needs-review, paused, completed). completed, next_steps, blockers, files_touched are comma-separated lists; project scopes the entry; context_notes holds anything the next session must know. It (1) upserts memory record task___state (task lowercased, spaces to underscores, first 40 chars) tagged task-active,handoff with high priority — repeat calls for the same task and project overwrite the previous handoff; (2) posts the payload to the crosslink channel "task-handoff"; (3) logs a milestone. Returns {"handoff_saved", "memory_key", "crosslink_channel", "next_session", "crosslink_posted"} — crosslink_posted is false when the crosslink post failed and the handoff is local-only. The next session resumes with sassy_memory_context plus sassy_crosslink_recv on "task-handoff". Use at session end or when context runs low — not as a substitute for sassy_memory_remember.

Input Schema

TableJSON Schema

Name	Required	Default
`task`	Yes
`status`	No	in-progress
`project`	No
`blockers`	No
`completed`	No
`next_steps`	No
`context_notes`	No
`files_touched`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`memory_key`	Yes
`next_session`	Yes
`handoff_saved`	Yes
`crosslink_posted`	Yes
`crosslink_channel`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.16.0Sep 22, 2026

addedOutput schema / properties / crosslink_posted

Added value: +{
+  "title": "Crosslink Posted",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "handoff_saved",
-  "memory_key",
-  "crosslink_channel",
-  "next_session"
-]New value: +[
+  "handoff_saved",
+  "memory_key",
+  "crosslink_channel",
+  "next_session",
+  "crosslink_posted"
+]

Changed7 schema fields changedv1.15.1Sep 18, 2026

addedOutput schema / properties / crosslink_channel

Added value: +{
+  "title": "Crosslink Channel",
+  "type": "string"
+}

addedOutput schema / properties / handoff_saved

Added value: +{
+  "title": "Handoff Saved",
+  "type": "boolean"
+}

addedOutput schema / properties / memory_key

Added value: +{
+  "title": "Memory Key",
+  "type": "string"
+}

addedOutput schema / properties / next_session

Added value: +{
+  "title": "Next Session",
+  "type": "string"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "handoff_saved",
+  "memory_key",
+  "crosslink_channel",
+  "next_session"
+]

changedOutput schema / title

Previous value: -"sassy_memory_handoffOutput"New value: +"HandoffResult"

First observedv0.1.0Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses the three side effects (upsert memory record, post to crosslink channel, log milestone), the overwrite behavior on repeat calls, the failure mode (crosslink_posted false, local-only handoff), and the exact memory key format. This goes well beyond the annotations, which only say readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false. The description adds critical behavioral context about mutation and failure handling.

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 description is dense but well-organized: it front-loads the mutating nature and the three writes, then details parameters, then behavior, then return value, then usage guidance. It is long but every sentence earns its place given the complexity of the tool. Slight deduction for density that could be split into clearer sections.

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?

The description covers the tool's purpose, parameters, side effects, return value, failure mode, and usage context. It even explains how the next session resumes. With an output schema present and this level of detail, nothing an agent needs to call it correctly is missing.

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%, so the description carries the full burden. It explains the required 'task' parameter, the status enum values, the comma-separated list format for several fields, the project scoping, and the context_notes purpose. It also explains how the task slug is derived (lowercased, spaces to underscores, first 40 chars), which is not in 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 'Mutating: runs the session-end handoff protocol — three writes at once,' which states a specific verb, resource, and behavior. It clearly distinguishes this from memory tools like sassy_memory_remember and sassy_memory_forget by naming the handoff protocol and the three writes.

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 says 'Use at session end or when context runs low — not as a substitute for sassy_memory_remember.' This gives clear when-to-use and when-not-to-use guidance, and names the alternative tool. It also explains the next-session resume flow, which helps an agent decide when to invoke it.

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

Deploy Server