Soul

Overview Schema Source Related Servers Discussions Admin

n2_boot

Initializes a named agent's session by loading handoff state, core memory, agent list, and KV-Cache context to resume work with shared project context.

Instructions

Boot sequence — loads soul-board handoff, entity/core memory, agent list, and KV-Cache context.

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": {
      "agent": "<agent>"
    },
    "name": "n2_boot"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	Yes	Agent name
`project`	No	Project name to load context for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv9.2.0Nov 4, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It lists what is loaded but says nothing about side effects (does boot register the agent or write state?), idempotency, permissions, or failure behavior for an unknown agent — significant gaps for an initialization tool with zero annotation coverage.

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?

A single front-loaded sentence that names the operation and its payload with no filler. It is efficient, though the em-dash list is dense and could be slightly clearer about ordering or dependencies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, one required, and no output schema, the description's enumeration of loaded resources usefully stands in for return-value explanation. It still omits what happens on failure or whether boot mutates state, leaving the picture incomplete for an initialization tool.

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 both 'agent' and 'project' are already documented in the schema. The description implies project-scoped context loading but adds no syntax, format, or default details beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('loads') and enumerates the concrete resources pulled in: soul-board handoff, entity/core memory, agent list, and KV-Cache context. This distinguishes it from single-resource siblings like n2_core_read or n2_kv_load, though it never explicitly names those alternatives.

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

Usage Guidelines3/5

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

'Boot sequence' implies it is called at session start, giving implied usage context. However, there is no explicit when-to-use/when-not-to-use guidance and no mention of how it relates to the individual loader siblings it aggregates.

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