slowave

Official

Overview Schema Source Related Servers Discussions Admin

slowave_commit

Close the current task and trigger offline memory consolidation, recording outcome, verification, and optional reusable procedure to preserve session knowledge.

Instructions

Close the current task and trigger offline memory consolidation.

Before calling, review whether the task revealed useful knowledge that a future task should retrieve directly. Store any such claims with slowave_remember; if none qualifies, commit normally. Commit records the task outcome and optional procedure, not a substitute for explicit claims. In particular, save a newly established requirement or decision that governs future tasks as a standalone claim before closing. Describing it in outcome_summary alone does not create that remembered claim. Call at the end of every task. If skipped, the idle-session reaper closes the session after SLOWAVE_SESSION_IDLE_TIMEOUT seconds (default 3600). Args: session_id: required active session from activate. final_goal: required confirmed goal. outcome: required success|partial|failure. outcome_summary: required standalone actual result. verification: required {status, summary, evidence_refs?}; status is verified|partially_verified|unverified. procedure: optional {version: 2, summary, context: {}, steps: [{summary}], caveats: []}; include only for a reusable method that was actually attempted. trajectory: optional executed-attempt trace of at most 32 action/observation entries, each {kind, summary, status?}. Must contain TASK actions/observations only. Do NOT include Slowave lifecycle bookkeeping (activate/recall/feedback/commit calls, "Activated the Slowave session." etc.) -- the server filters those out and reports the count as trajectory_lifecycle_filtered. If you have no task-level actions, omit the trajectory. Returns: session_id: the session that was closed. episodes_formed: number of episodic memories created. feedback_status: complete for normal closure. committed: true when the session outcome was recorded. outcome: confirmed success, partial, or failure outcome. verification_status: confirmed verification status. operation: closed for a new close or updated for an already-ended session. trajectory_lifecycle_filtered: number of lifecycle entries removed, when any were filtered. already_ended: true when the session had already been closed.

Input Schema

Name	Required	Description	Default
`outcome`	Yes
`procedure`	No
`final_goal`	Yes
`session_id`	Yes
`trajectory`	No
`verification`	Yes
`outcome_summary`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.20.5Oct 14, 2026

addedInput schema / $defs / CommitProcedure / properties / deduplication_key

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[a-z][a-z0-9_.:-]{0,63}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Deduplication Key"
+}

First observedv0.20.3Sep 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description must carry the full behavioral burden, and it does substantively: it discloses the memory-consolidation side effect, the idle-reaper timeout with default, lifecycle-entry filtering during trajectory capture, and non-idempotent-looking-but-tolerated re-commit behavior ('operation: closed for a new close or updated for an already-ended session'). It stops short of stating permission/auth requirements or whether closing is irreversible, which is why this is a 4 rather than a 5.

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?

Front-loaded with the core action and the pre-call decision rule, then a structured Args list. It is long, and the Returns block largely restates fields already carried by the output schema, which is wasted space, but the prose itself is dense and each guidance sentence about the remember-vs-commit decision earns its place.

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 7 parameters, 5 required, nested verification/procedure objects and 0% schema description coverage, the description supplies the missing semantics for every required and optional field plus omission guidance ('If you have no task-level actions, omit the trajectory'). The output schema covers return values, so the description need not explain them further.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to compensate, and the Args block does: it labels session_id as the active session from activate, final_goal as the *confirmed* goal, explains outcome_summary as a 'standalone actual result', and details verification's status enum and procedure/trajectory content rules. The trajectory constraint (task-level only, max 32, no lifecycle bookkeeping) is genuinely additive 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?

Opens with a specific verb+resource: 'Close the current task and trigger offline memory consolidation.' It also distinguishes itself from the sibling slowave_remember by stating what commit does *not* store (explicit claims). An agent can identify this as the terminal/close operation without opening the schema.

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?

Gives explicit when-to-use ('Call at the end of every task'), a when-to-use-alternative rule (store reusable knowledge with slowave_remember first, commit if nothing qualifies), and a when-not consequence (the idle-session reaper closes after SLOWAVE_SESSION_IDLE_TIMEOUT). It even handles the edge case of an already-ended session via the `operation`/`already_ended` semantics.

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

Deploy Server