Skip to main content
Glama
Sign In
contextium-mcp-server

contextium-mcp-server

Official
by contextium-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

delete_phase

Remove a specific phase from a project plan using its phase ID. Use this to delete individual work items rather than bulk removal of completed phases.

Instructions

Delete a single phase from a project plan by its phase ID. Use this to remove a specific work item. To bulk-remove completed work, use delete_done_phases instead.

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": {
      "phaseId": "<phaseId>"
    },
    "name": "delete_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
phaseIdYesPhase ID (from list_phases or get_project)
workspaceIdNoWorkspace ID. Defaults to your configured workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'delete', which is inherently destructive, but lacks details on permanence, permissions, or cascading effects on associated tasks.

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 concise sentences: first states the core action, second provides usage guidance and names the alternative. Every sentence is necessary and well-ordered.

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?

For a simple delete tool with two documented parameters and no output schema, the description is sufficient. It covers what, how, and alternatives. Could mention if the operation is reversible or requires confirmation, but not essential.

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?

The input schema has 100% coverage, already describing both parameters (phaseId and workspaceId). The description adds no extra meaning beyond 'by its phase ID', so it meets the baseline but doesn't add value.

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', the resource 'single phase', and the method 'by its phase ID'. It differentiates from the sibling tool 'delete_done_phases' by noting it's for individual removal.

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

Usage Guidelines5/5

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

Explicitly states when to use (to remove a specific work item) and when not (use delete_done_phases for bulk removal). Provides a clear alternative sibling.

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