Mcp-Omega-Brain

Overview Schema Source Related Servers Discussions Admin

omega_write_handoff

Creates a SHA-256 sealed handoff document that auto-loads on server restart to preserve session context and progress.

Instructions

Creates a SHA-256 sealed handoff document that auto-loads on the next server restart via omega://session/preload. Use this at the end of a session to ensure seamless context continuity for the next session. Returns JSON with fields: handoff_hash (hex string), file_path (string).

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": {
      "task": "<task>",
      "summary": "<summary>"
    },
    "name": "omega_write_handoff"
  }
}

Input Schema

Name	Required	Description
`task`	Yes	Task title for the handoff, e.g. 'OAuth2 migration phase 2'.
`summary`	Yes	Concise summary of progress and current state for the next session.
`decisions`	No	Key decisions the next session should know about.
`files_modified`	No	Files changed during this session.
`next_steps`	No	Ordered list of recommended next actions.
`conversation_id`	No	Optional external conversation tracking ID.

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 3, 2026
Removedv2.1.1Apr 14, 2026

Changed6 schema fields changedv1.0.2Apr 14, 2026

changedInput schema / properties / conversation_id / description

Previous value: -"Optional conversation identifier for cross-referencing with external conversation tracking systems."New value: +"Optional external conversation tracking ID."

changedInput schema / properties / decisions / description

Previous value: -"Key architectural or implementation decisions that the next session should be aware of."New value: +"Key decisions the next session should know about."

changedInput schema / properties / files_modified / description

Previous value: -"Files that were changed during this session, so the next session knows what to review."New value: +"Files changed during this session."

changedInput schema / properties / next_steps / description

Previous value: -"Ordered list of recommended next actions for the continuation session."New value: +"Ordered list of recommended next actions."

changedInput schema / properties / summary / description

Previous value: -"Concise summary of what was accomplished and the current state. This is the primary context the next session will receive."New value: +"Concise summary of progress and current state for the next session."

changedInput schema / properties / task / description

Previous value: -"The task that was being worked on, used as the handoff title."New value: +"Task title for the handoff, e.g. 'OAuth2 migration phase 2'."

Changed6 schema fields changedv1.0.1Apr 14, 2026

addedInput schema / properties / conversation_id / description

Added value: +"Optional conversation identifier for cross-referencing with external conversation tracking systems."

addedInput schema / properties / decisions / description

Added value: +"Key architectural or implementation decisions that the next session should be aware of."

addedInput schema / properties / files_modified / description

Added value: +"Files that were changed during this session, so the next session knows what to review."

addedInput schema / properties / next_steps / description

Added value: +"Ordered list of recommended next actions for the continuation session."

addedInput schema / properties / summary / description

Added value: +"Concise summary of what was accomplished and the current state. This is the primary context the next session will receive."

addedInput schema / properties / task / description

Added value: +"The task that was being worked on, used as the handoff title."

First observedv1.0.0Apr 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations present, so description carries full burden. It discloses the creation (write operation), the SHA-256 sealing, and the auto-load behavior on restart. However, it does not mention potential side effects or permissions.

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?

Three sentences with no extraneous information. Front-loaded with the primary action and key property (SHA-256 sealed handoff). Efficient and well-structured.

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?

The description explains the tool's purpose, usage timing, and return format. For a tool with 6 parameters and no output schema, it is fairly complete. Could mention error conditions, but overall adequate.

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 the schema already describes each parameter (task, summary, etc.). The description adds overall context but does not provide additional meaning 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?

Description clearly states it creates a SHA-256 sealed handoff document that auto-loads on server restart. The specific verb 'creates', resource 'handoff document', and the unique URI 'omega://session/preload' make the purpose distinct from sibling tools like omega_seal_run or omega_log_session.

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?

Explicitly instructs to use 'at the end of a session to ensure seamless context continuity for the next session.' Provides clear when-to-use guidance, though it does not discuss alternatives or when not to use.

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