Skip to main content
Glama
Sign In
HacknPlan MCP

HacknPlan MCP

by jompereira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_board

Permanently delete a board from a project, with the option to also remove all its work items.

Instructions

Permanently delete a board

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": {
      "projectId": "<projectId>",
      "boardId": "<boardId>"
    },
    "name": "delete_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYes
projectIdYes
removeWorkItemsNoAlso delete all work items on this board (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description must cover behavioral traits. It mentions permanence but omits consequences like the optional deletion of work items (via removeWorkItems parameter), required permissions, or any irreversible effects beyond the board itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise and front-loaded, but it could briefly mention the optional removal of work items without becoming verbose.

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?

For a deletion tool with three parameters and no output schema, the description is overly minimal. It lacks detail on success/failure outcomes, side effects, and the significance of the removeWorkItems option.

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

Parameters2/5

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

With only 33% schema description coverage and no parameter details in the tool description, agents lack guidance for the boardId and projectId parameters. The removeWorkItems parameter is described in the schema but not reiterated in the description, leaving a gap.

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 'Permanently delete a board' uses a specific verb and resource, clearly distinguishing it from sibling delete tools for other entities like categories or 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 Guidelines3/5

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

The description implies the tool is for deleting boards but provides no guidance on when to use it versus alternatives like close_board, nor any prerequisites or exclusions.

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