hacknplan-mcp

delete_category

Delete a work-item category from a HacknPlan project. Destructive action requiring confirmation; use it to remove default categories such as Audio and Narrative.

Instructions

Delete a work-item category. Destructive. confirm=true required. (Useful to remove the game-dev defaults — Audio, Narrative, etc.)

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_id": "<project_id>",
      "category_id": "<category_id>"
    },
    "name": "delete_category"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`project_id`	Yes
`category_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It explicitly states 'Destructive' and 'confirm=true required', which are crucial behavioral traits for a deletion operation. It could elaborate on consequences for associated work items, but the destructive warning and confirmation requirement are strong disclosures.

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 two sentences, front-loaded with the action and safety warning. Every sentence adds value: the action, the destructive nature, the confirm requirement, and a practical use case. There is no redundant or filler content.

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 simple deletion tool with three parameters and no output schema, the description covers purpose, destructiveness, confirm requirement, and a suggested use case. It doesn't mention what happens to work items assigned to the category, but 'Destructive' hints at potential data impact. Overall, it is fairly complete for the tool's complexity.

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 0%, so the description must compensate. 'confirm=true required' clarifies the boolean confirm parameter's necessity and role. The other parameters (project_id, category_id) are self-evident from their names and the schema, so the description adds sufficient meaning for the key non-obvious parameter.

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 'Delete a work-item category', which is a specific verb and resource. It distinguishes this tool from siblings like delete_tag, delete_stage, and delete_work_item by specifying the target as a work-item category.

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

Usage Guidelines4/5

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

It provides a concrete use case: 'Useful to remove the game-dev defaults — Audio, Narrative, etc.' This gives clear context for when this tool is appropriate. It doesn't explicitly mention alternatives, but the use case implies its specific role without needing exclusions.

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

Deploy Server