Skip to main content
Glama

Complete Phase

complete_phase

Mark the current project phase as completed and optionally advance to the next phase, with a notes summary of accomplishments for clear handoff.

Instructions

Mark the current phase as completed and optionally advance to the next phase.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "complete_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
notesNoSummary of what was accomplished in this phase.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It never says whether completion is reversible, what preconditions must hold (e.g. phase must be in progress), how 'notes' is persisted, or whether the advance step can fail independently.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient, though the trailing 'optionally advance' clause introduces ambiguity rather than value.

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

Completeness2/5

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

The output schema covers return values, but the description promises an optional advance while the schema exposes no parameter controlling that behavior. For a state-mutating lifecycle tool with zero annotations, this leaves the agent unable to predict the tool's actual effects relative to next_phase.

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%, so 'path' and 'notes' are already documented in the schema; the description adds no format, default, or constraint detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb and resource ('Mark the current phase as completed') plus a secondary effect ('optionally advance to the next phase'). It is reasonably distinguishable from complete_task and set_phase, but it blurs against the sibling next_phase since it does not say how the two relate.

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

Usage Guidelines2/5

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

No guidance on when this should be called instead of set_phase, next_phase, or complete_task. An agent must infer whether advancing requires a separate next_phase call or is handled here.

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