Skip to main content
Glama

Next Phase

next_phase

Marks the current project phase complete and advances the workflow to the next phase in sequence, accepting the next phase name and optional description.

Instructions

Mark current phase as complete and advance to the next phase in sequence.

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": {
      "phase_name": "<phase_name>"
    },
    "name": "next_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
phase_nameYesName of the next phase.
descriptionNoWhat the next phase involves.

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 for a mutation tool. It never says what happens if the current phase is already complete, what occurs at the final phase, whether phase_name must be a new or existing phase, or whether the change is reversible.

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 or redundancy. It is efficient, though its brevity is part of why the behavioral gaps exist.

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?

An output schema exists, so return values need not be explained. But for a phase-transition mutation with zero annotations, the definition omits critical context: sequencing rules, terminal-phase behavior, and error conditions an agent would need before invoking it.

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%, with path, phase_name, and description all documented inline, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as whether phase_name must match an existing phase or how description is rendered into the phase record.

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?

The description uses a concrete verb pair (mark complete, advance) on a specific resource (phase), so the operation itself is unambiguous. It does not, however, distinguish this from siblings such as complete_phase or set_phase, which appear to cover overlapping ground.

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?

There is no guidance on when to call next_phase versus complete_phase or set_phase, which are listed as siblings with clearly related semantics. The agent must infer the routing decision entirely from tool names.

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