Skip to main content
Glama
Sign In
HacknPlan MCP Server

HacknPlan MCP Server

by Lint111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

confirm_deletion

Execute a staged deletion after user confirmation by providing the confirmation token and acknowledging with 'DELETE' or 'CONFIRM'.

Instructions

Execute a staged deletion after user confirmation. Requires the confirmation token from batch_delete_work_items and acknowledged must be "DELETE" or "CONFIRM".

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": {
      "confirmationToken": "<confirmationToken>",
      "acknowledged": "<acknowledged>"
    },
    "name": "confirm_deletion"
  }
}

Input Schema

NameRequiredDescriptionDefault
authCodeNoOptional authentication code for 2FA (future feature)
acknowledgedYesMust be "DELETE" or "CONFIRM" to proceed with deletion
confirmationTokenYesThe confirmation token from batch_delete_work_items

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv7.2.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses it's a staged deletion (destructive) and necessary inputs, but does not mention idempotency, error handling, or success behavior.

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 sentences, no filler, front-loads main purpose and prerequisites. Every sentence earns its place.

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?

No output schema, but description covers core purpose and inputs. Could add minimal context on result, but sufficient for a confirmation step.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds value by clarifying the dependency between confirmationToken and batch_delete_work_items, and restating the required acknowledged values.

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?

Description uses specific verb 'Execute' and resource 'staged deletion', clearly distinguishing from sibling tools like cancel_deletion or batch_delete_work_items.

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?

States prerequisite (confirmation token from batch_delete_work_items) and required acknowledged value. Could explicitly mention when not to use, but implied by requirement for confirmation.

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

Deploy Server

Other Tools