Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_set_phase

Transition the AgLoop agent framework to a new operational phase. Use this tool to manage agent states and execution workflows in VS Code Copilot.

Instructions

Transition to a new phase. COORDINATOR ONLY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phaseYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the `agloop_set_phase` tool, which acts as a handler. It transitions the state phase using the `StateManager`.
    def agloop_set_phase(phase: str) -> str:
        """Transition to a new phase. COORDINATOR ONLY."""
        result = _sm().set_phase(phase)
        if not result:
            return json.dumps({"error": "Failed to set phase"})
        return json.dumps(result, indent=2)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'COORDINATOR ONLY', hinting at authorization needs, but doesn't disclose other behavioral traits such as whether this is a destructive mutation, potential side effects, rate limits, or what happens on success/failure. The term 'Transition' implies a state change, but details are vague, leaving gaps in understanding the tool's behavior.

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?

The description is very concise with two short phrases, making it front-loaded and easy to parse. However, it might be overly terse, as it lacks necessary details for clarity. Every word earns its place, but the brevity comes at the cost of completeness, slightly reducing effectiveness.

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 the tool's complexity (a state transition with 1 parameter) and the presence of an output schema (which likely handles return values), the description is minimally adequate. However, with no annotations and low schema coverage, it should provide more context on usage, parameters, and behavior. It meets a basic threshold but has clear gaps in explaining the tool's full scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, so the schema provides no details about 'phase'. The description doesn't add any meaning beyond the schema—it doesn't explain what 'phase' represents (e.g., a string identifier, enum values, or format), its valid values, or how it affects the transition. This fails to compensate for the low schema coverage.

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

Purpose3/5

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

The description states the tool 'Transition[s] to a new phase', which provides a basic verb+action. However, it lacks specificity about what resource or system is being transitioned (e.g., an agent, task, or process), and it doesn't clearly distinguish from siblings like 'agloop_update_task' or 'agloop_get_state', which might involve state changes. The phrase 'COORDINATOR ONLY' adds some context but doesn't fully clarify the purpose.

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?

The description includes 'COORDINATOR ONLY', which implies a usage restriction based on role, but it doesn't explain when to use this tool versus alternatives. For example, it doesn't specify if this is for starting, pausing, or completing phases, or how it differs from tools like 'agloop_update_task' that might also modify states. No explicit guidance on prerequisites or exclusions is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zebbern/agloop-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server