HacknPlan MCP Server

import_deletion_cache

Import a recovery cache from a JSON file, with options to merge into existing cache or replace it entirely. File format is validated.

Instructions

Import recovery cache from JSON file. Supports merge (add to existing) or replace (clear then import) modes. Validates file format.

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": {
      "filePath": "<filePath>",
      "mode": "<mode>"
    },
    "name": "import_deletion_cache"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes	merge: add to existing cache, replace: clear cache first
`filePath`	Yes	Absolute path to import file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv7.2.0Jul 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Discloses file format validation and the replace mode's destructive nature, but lacks details on error handling (e.g., missing file, invalid JSON) and does not explicitly state that the tool modifies data. With no annotations, the description carries full burden.

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 short sentences, each adding unique value: purpose, modes, and validation. No wasted words, front-loaded with the core action.

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?

Covers purpose, modes, and validation adequately for a simple import tool. Could mention prerequisites (e.g., file existence) or error behavior, but the description is sufficient for agent invocation.

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% and the description reiterates the mode parameter's semantics. Does not add new meaning beyond what the schema already provides, earning a baseline 3.

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?

Clearly states it imports a recovery cache from a JSON file with distinct merge/replace modes. Differentiates from sibling tools like export_deletion_cache and clear_deletion_cache.

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?

Describes the two modes (merge/replace) but does not explicitly guide when to use this tool versus alternatives like clear_cache or clear_deletion_cache, nor provides exclusions.

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

Deploy Server