HacknPlan MCP Server

export_deletion_cache

Export recovery cache to JSON file for backup or migration. Optionally limit export to a specific project.

Instructions

Export recovery cache to JSON file. Supports project-specific export. Useful for backup or migration.

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>"
    },
    "name": "export_deletion_cache"
  }
}

Input Schema

Name	Required	Description	Default
`filePath`	Yes	Absolute path for export file (e.g., /path/to/backup.json)
`projectId`	No	Optional: only export entries for this project

Schema Changelog

Changes observed during successful MCP inspections.

First observedv7.2.0Jul 13, 2026

TDQS

B3.4/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 full burden. It fails to disclose behavioral details such as whether the export overwrites existing files, permissions required, or the JSON structure. The inconsistency between 'deletion_cache' in name and 'recovery cache' in description adds confusion.

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?

The description is concise with two sentences: the first defines the core action, the second adds optional filtering and use cases. No redundant information.

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?

The description is incomplete given the lack of annotations and output schema. It does not explain what data is exported, error conditions, or the relationship to import_deletion_cache. The naming inconsistency ('deletion_cache' vs 'recovery cache') undermines clarity.

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 the description adds marginal value. It reinforces the project-specific export but provides no additional details about filePath format, validation, or side effects 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?

The description clearly states the action ('Export recovery cache to JSON file') and supports project-specific export, which distinguishes it from sibling tools like import_deletion_cache or clear_deletion_cache. The verb-resource pair is precise.

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?

The description provides usage context ('Useful for backup or migration') but does not explicitly state when not to use it or mention alternatives like import_deletion_cache for restore. The guidance is implicit rather than explicit.

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

Deploy Server