Planning System MCP Server

delete_plan

Remove a specific plan from the Planning System MCP Server by providing its plan ID. This tool helps manage project planning data by eliminating outdated or unnecessary plans.

Instructions

Delete a plan

Input Schema

TableJSON Schema

Name	Required	Description	Default
`plan_id`	Yes	Plan ID to delete

Implementation Reference

src/tools.js:538-545 (handler)
The primary MCP tool handler for 'delete_plan'. Extracts the plan_id from input arguments, delegates to the apiClient's deletePlan method, and returns a formatted success response.
```
if (name === "delete_plan") {
  const { plan_id } = args;
  await apiClient.plans.deletePlan(plan_id);
  return formatResponse({
    success: true,
    message: `Plan ${plan_id} deleted successfully`
  });
}
```

src/tools.js:157-167 (registration)

Registration of the 'delete_plan' tool in the MCP server's ListToolsRequestHandler, including name, description, and input schema.

{
  name: "delete_plan",
  description: "Delete a plan",
  inputSchema: {
    type: "object",
    properties: {
      plan_id: { type: "string", description: "Plan ID to delete" }
    },
    required: ["plan_id"]
  }
},

src/tools.js:160-166 (schema)

Input schema validation for the 'delete_plan' tool, requiring a 'plan_id' string.

inputSchema: {
  type: "object",
  properties: {
    plan_id: { type: "string", description: "Plan ID to delete" }
  },
  required: ["plan_id"]
}

src/api-client.js:101-103 (helper)
API client helper function apiClient.plans.deletePlan that performs the actual HTTP DELETE request to the /plans/{planId} endpoint.
```
deletePlan: async (planId) => {
  await apiClient.delete(`/plans/${planId}`);
}
```

Tool Definition Quality

C2/5.0

Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. 'Delete a plan' implies a destructive, irreversible mutation, but it doesn't state permission requirements, whether deletion is permanent, what happens to associated data (e.g., child nodes), or error conditions. This is inadequate for a destructive operation with zero annotation coverage.

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 extremely concise at three words, with no wasted language. It's front-loaded with the core action ('Delete'), though this brevity comes at the cost of completeness. Every word earns its place by directly stating the tool's function without redundancy.

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

Completeness1/5

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

Given the tool's destructive nature, lack of annotations, absence of an output schema, and multiple sibling tools, the description is severely incomplete. It doesn't explain the tool's behavior, outcomes, or integration with other tools (e.g., what happens to nodes in a deleted plan), making it inadequate for safe and effective use by an AI agent.

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 100%, with the single parameter 'plan_id' clearly documented in the schema as 'Plan ID to delete'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for adequate but unenhanced parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a plan' is a tautology that merely restates the tool name without adding specificity. It doesn't distinguish this tool from other deletion tools like 'delete_node' or clarify what type of plan is being deleted (e.g., project plan, subscription plan). While the verb 'Delete' is clear, the lack of resource specificity makes this minimally informative.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a plan ID), when not to use it (e.g., for archiving instead), or how it relates to sibling tools like 'delete_node', 'list_plans', or 'create_plan'. This leaves the agent with no context for appropriate tool selection.

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

Install Server

Other Tools

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TAgents/agent-planner-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server