Soul

Overview Schema Source Related Servers Discussions Admin

n2_kv_load

Loads the most recent KV-Cache snapshot for a project and returns compressed context for AI agents resuming work or sharing session state.

Instructions

Load the most recent KV-Cache snapshot for a project. Returns compressed 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": {
      "project": "<project>"
    },
    "name": "n2_kv_load"
  }
}

Input Schema

Name	Required	Description
`agent`	No	Identity; defaults to boot identity
`level`	No	Progressive level: L1 (minimal), L2 (standard), L3 (full), auto (default)
`budget`	No	Token budget for context (default: 2000)
`project`	Yes	Project name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv9.2.0Nov 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden and only discloses that the newest snapshot is returned in compressed form. It says nothing about what happens when no snapshot exists, whether loading mutates state or evicts anything, how 'level' and 'budget' trade off, or whether the returned context is truncated.

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?

Two short sentences with no filler and the purpose front-loaded. The closing sentence about returning compressed context is slightly vague but not wasted.

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 four-parameter read-style tool with fully documented schema, no output schema, and no annotations, the definition covers the core action, though it leaves the level/budget interaction and the empty-cache case implicit. The gap is moderate rather than severe because the schema supplies the parameter detail.

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 all four parameters are already documented in the schema, which sets the baseline at 3. The description adds no parameter-level meaning beyond the schema, so it does not exceed that baseline.

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?

States a specific verb and resource ('Load the most recent KV-Cache snapshot') plus the scope ('for a project'), so the agent knows exactly what it does. It does not differentiate itself from KV siblings such as n2_kv_search, n2_kv_restore, or n2_kv_gc, which would be needed for a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to load versus search, restore, or read from the cache; the agent must infer that from the verb alone. No prerequisites, no exclusions, and no named alternatives despite seven KV-related siblings.

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