Soul

Overview Schema Source Related Servers Discussions Admin

n2_kv_backup

Backs up KV-Cache data to a portable SQLite database with incremental backup support, helping preserve project context for restoration and reuse.

Instructions

Backup KV-Cache data to a portable SQLite DB. Supports incremental backups.

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_backup"
  }
}

Input Schema

Name	Required	Description	Default
`full`	No	Force full backup (ignore incremental)
`project`	Yes	Project name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv9.2.0Nov 4, 2026

TDQS

C2.9/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, yet it omits where the SQLite file is written, whether an existing backup is overwritten, permission or disk-space requirements, and whether the call is long-running. The only behavioral disclosure is the implicit default-to-incremental semantics, which is thin for a write-side operation.

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?

Two short sentences, front-loaded with the operation and its output format, with zero filler. Nothing could be removed without losing content.

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

Completeness2/5

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

For a low-complexity tool this is close, but with no annotations and no output schema, the description is the only source of behavioral information and it never says where the backup lands or what the call reports back. That destination detail is precisely what an agent needs before invoking a backup.

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 coverage is 100%, so both parameters are already documented in the input schema, giving a baseline of 3. The description's mention of incremental backups adds light context for interpreting the `full` flag, but no extra detail about what a full backup costs or implies.

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 ('Backup KV-Cache data') plus the output form ('portable SQLite DB'), which is more than a restatement of the name. However, it never distinguishes itself from the adjacent n2_kv_restore and n2_kv_backup_list tools, so an agent must infer the boundary from the names alone.

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 explicit when-to-use guidance: nothing says whether to back up before destructive operations, how this relates to n2_kv_restore, or when to consult n2_kv_backup_list. The phrase 'Supports incremental backups' implies a default mode but does not route the agent among alternatives.

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