contextium-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

update_phase_status

Update a project phase status to track progress. Setting to 'done' automatically logs the completion time.

Instructions

Update the status of a project phase. Valid statuses: pending, in_progress, done, blocked. Use this to progress phases as work is completed. Setting a phase to "done" automatically records the completion time.

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>",
      "status": "<status>"
    },
    "name": "update_phase_status"
  }
}

Input Schema

Name	Required	Description
`status`	Yes	New status for the phase.
`phaseId`	Yes	Phase ID (from list_phases or get_project)
`workspaceId`	No	Workspace ID. Defaults to your configured workspace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 10, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Discloses that setting status to 'done' auto-records completion time, which is valuable. However, does not mention if the operation is reversible, requires specific permissions, or returns data. Adequate for a simple state update.

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 front-loading the purpose and key behaviors. Every sentence adds value: first sentence defines the action and valid states, second gives usage context and a notable side effect.

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?

No output schema, but description covers core purpose, valid statuses, side effect of 'done', and usage context. Lacks mention of error conditions, prerequisites (e.g., phase must exist), or return value. Still sufficient for a simple tool with few parameters.

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 already describes all 3 parameters with 100% coverage. The description adds the auto-record behavior for 'done' status, but that is a behavioral trait rather than parameter-specific detail. Minimal added value over schema.

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?

Clearly states the action ('Update the status of a project phase'), resource ('project phase'), and lists valid statuses. Distinguishes from siblings like 'update_task_status' by focusing on phases and mentioning the auto-record behavior for 'done'.

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?

Explicitly says to use it to progress phases as work is completed. Lacks explicit when-not-to-use or alternative tool suggestions, but the context is clear for typical workflow.

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

Deploy Server