HacknPlan MCP Server

reopen_milestones

Reopen one or multiple closed milestones in your project. Supports batch operations with error handling.

Instructions

Reopen one or more closed milestones (array-based). Single-item and batch calls use the same interface. Returns unified response with items array, counts, and per-item errors.

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": {
      "items": "<items>"
    },
    "name": "reopen_milestones"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	Array of milestones to reopen (1-100 items)
`projectId`	No	The project ID (optional if HACKNPLAN_DEFAULT_PROJECT set)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv7.2.0Jul 13, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description should disclose behavioral traits. It describes the return format (items array, counts, per-item errors), but lacks details on permissions, reversibility, or side effects. It acknowledges it is a mutation operation.

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 redundant words, front-loaded with the core action. Excellent conciseness.

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?

Covers the key aspects: action, parameters (via schema), return structure. Missing only minor context like typical use case prerequisites. Adequate for 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 100%, so baseline is 3. The description adds that the interface is array-based and handles single/batch, but does not add meaning beyond the schema's parameter descriptions.

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 the action (reopen), the resource (milestones), and the scope (array-based, single or batch). It distinguishes from sibling tools like close_milestones, update_milestones, and delete_milestones.

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 mentions that single-item and batch calls use the same interface, and implicitly that it is for closed milestones. However, it does not explicitly exclude cases where milestones are already open.

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

Deploy Server