Skip to main content
Glama

Set Phase

set_phase

Defines the active development phase so only tasks belonging to that phase are considered in scope.

Instructions

Set the current active development phase. Only tasks in this phase are considered 'in scope'.

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": "set_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
phase_nameYesName of the phase (e.g. 'Phase 4 — Activity Creation').
descriptionNoWhat this phase involves.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key behavioral consequence — only tasks in this phase count as in scope — which is genuinely useful context beyond the schema. It leaves unstated whether the phase must already exist, whether setting creates or mutates state, and what happens to tasks belonging to previously active phases.

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 short sentences with the action first and the consequence second; nothing is wasted and the important scoping rule is front-loaded.

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?

An output schema exists, so return values need not be explained, and all three parameters are documented. What is missing for a stateful phase-management tool is the relationship to the phase lifecycle — whether the phase must pre-exist, whether it can be switched repeatedly, and how it interacts with complete_phase or 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 coverage is 100%, so path, phase_name, and description are already documented in the schema, including an example value for phase_name. The description adds no additional meaning about parameter behavior, so the baseline of 3 applies.

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+resource ("Set the current active development phase") that is immediately understandable. It does not, however, differentiate itself from near-neighbors in the sibling list such as get_current_phase, next_phase, complete_phase, or list_phases, so an agent must infer which of these to call.

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?

Usage is implied rather than stated: the sentence about in-scope tasks hints at why one would set a phase. There is no explicit when-to-use guidance, no preconditions, and no mention of how this differs from next_phase or complete_phase.

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