Skip to main content
Glama
Sign In
hacknplan-mcp

hacknplan-mcp

by mtuska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_milestone

Delete a milestone in a project, ungrouping associated work items (which are not deleted). Requires confirmation.

Instructions

Delete a milestone. Destructive (work items are un-grouped, not deleted). confirm=true required.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
project_idYes
milestone_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses the destructive nature and nuances: 'work items are un-grouped, not deleted' and 'confirm=true required.' This goes beyond a simple deletion notice and clearly explains the behavioral impact on work items.

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, front-loaded with the core action, followed by essential warnings and a requirement. No filler or redundant content; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete tool with no output schema, the description covers the key aspects: the action, destructiveness, effect on associated work items, and the required confirmation. Combined with the schema's parameter definitions, it provides sufficient context for safe and correct invocation.

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 0%, so the description must compensate. It explains the 'confirm' parameter's required value and its role, but does not describe 'project_id' or 'milestone_id'. Their names are self-explanatory, so partial compensation is provided, but not full coverage.

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 states 'Delete a milestone' with a specific verb and resource, clearly distinguishing the action from sibling tools like close_milestone, reopen_milestone, and update_milestone. The purpose is unambiguous.

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 a precondition ('confirm=true required') and a cautionary note about destructiveness, but does not explicitly instruct when to use this tool versus alternatives like close_milestone. Some context is implied, but no exclusions or alternative tool references are given.

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