Skip to main content
Glama
Sign In
Plane MCP Server

Plane MCP Server

by leigangzhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_project_estimate_point

Remove an estimate point from a project by specifying the project, estimate, and estimate point IDs. Permanently deletes the point from Plane.

Instructions

Delete a single estimate point.

Args: project_id: UUID of the project estimate_id: UUID of the estimate estimate_point_id: UUID of the estimate point to delete

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>",
      "estimate_id": "<estimate_id>",
      "estimate_point_id": "<estimate_point_id>"
    },
    "name": "delete_project_estimate_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
estimate_idYes
estimate_point_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states only that the tool deletes a single estimate point, but does not mention irreversibility, required permissions, cascading effects, or any other behavioral traits. For a destructive operation, this is a significant gap.

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 concise and well-structured: a one-line summary followed by an Args block with clear parameter explanations. Every sentence provides necessary information, and no redundant content exists.

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

Completeness3/5

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

For a simple delete operation with three parameters, the description adequately explains what the tool does and what each parameter means. However, it lacks usage guidance and behavioral transparency (e.g., irreversibility, permissions), and no output schema or return behavior is described. It meets the minimum viable level but no more.

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?

The schema only lists parameters as strings with no descriptions, while the description explains each parameter: project_id is UUID of the project, estimate_id is UUID of the estimate, and estimate_point_id is UUID of the estimate point to delete. This adds meaningful context and compensates for the 0% schema 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 clearly states the verb 'Delete' and the specific resource 'a single estimate point', which distinguishes it from sibling tools like delete_project_estimate (deleting a whole estimate) and update_project_estimate_point. The one-line summary is direct and 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 implies use when deleting one estimate point, but it does not explicitly state when to use this tool versus alternatives. No exclusions or alternative tool references are given, leaving the agent to infer from the name. This meets the 'implied usage' level, but not clear guidance.

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