contextium-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

add_phase

Adds a phase to a workflow's project plan, appending it to the end. Automatically creates a project plan if one does not exist.

Instructions

Add a phase (work item) to a workflow's project plan. Phases are appended at the end of the existing list. If the workflow has no project plan yet, one is created automatically.

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": {
      "workflowId": "<workflowId>",
      "title": "<title>"
    },
    "name": "add_phase"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Phase title — short, actionable description of the work.
`workflowId`	Yes	Workflow ID
`description`	No	Optional longer description or acceptance criteria.
`workspaceId`	No	Workspace ID. Defaults to your configured workspace.
`assignedAgentId`	No	Optional agent ID to assign this phase to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 10, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It discloses that phases are appended and auto-creates a plan, but lacks details on side effects, permissions, error handling, return values, or what happens to optional parameters. Important behavioral traits for a mutation tool are omitted.

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, both directly informative. The first sentence states the core purpose, the second adds key behavioral detail. No filler or redundancy.

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?

Given 5 parameters (2 required), no output schema, and no annotations, the description provides adequate high-level behavior but lacks return value info, error handling, and specific parameter interactions. It is minimally complete for the tool's complexity.

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 each parameter has a description. The tool description adds context about appending and auto-creation, but does not enhance parameter semantics beyond what the schema provides. Baseline score is appropriate.

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 'Add' and the resource 'phase (work item) to a workflow's project plan'. It distinguishes from sibling tools like delete_phase or update_phase_status by specifying the action and resource.

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 mentions phases are appended at the end and that a project plan is auto-created if missing. However, it provides no explicit guidance on when to use this tool versus alternatives like add_task, nor does it mention prerequisites or exclusions.

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

Deploy Server