HacknPlan MCP Server

get_deletion_cache_stats

Check recovery cache statistics including capacity, entries by project and status, and age ranges to monitor cache health.

Instructions

View recovery cache statistics including capacity, entries by project/status, and age ranges. Useful for monitoring cache health.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_deletion_cache_stats"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	No	Optional: filter stats for specific project

Schema Changelog

Changes observed during successful MCP inspections.

First observedv7.2.0Jul 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read-only view operation, but lacks detail on authentication needs, rate limits, or whether the stats are aggregated or per-project.

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 concise sentences, front-loaded with the action and specific details. Every word adds value, no fluff.

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?

No output schema exists, so the description should explain return format. It mentions capacity, entries, age ranges, but not structure or pagination. For a simple stats view, this is minimally adequate.

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% (one parameter described as optional filter). The description adds 'by project/status' which hints at usage, but does not enhance meaning beyond the schema's description.

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 uses a specific verb 'View' and resource 'recovery cache statistics', listing concrete aspects (capacity, entries by project/status, age ranges). It clearly differentiates from sibling tools like clear_deletion_cache or export_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?

The description states it is 'useful for monitoring cache health', implying context. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor mention alternatives.

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

Deploy Server