Skip to main content
Glama
goto-software

plane-mcp-server

by goto-software
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

unarchive_cycle

Restore an archived cycle in a project by providing the project and cycle IDs.

Instructions

Unarchive a cycle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
cycle_idYesUUID of the cycle

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • plane_mcp/tools/cycles.py:304-318 (handler)
    The `unarchive_cycle` tool handler function. It is decorated with @mcp.tool(), takes project_id and cycle_id as parameters, retrieves the Plane client and workspace slug via get_plane_client_context(), then calls client.cycles.unarchive() to unarchive the cycle. Returns a boolean indicating success.
    @mcp.tool()
def unarchive_cycle(project_id: str, cycle_id: str) -> bool:
    """
    Unarchive a cycle.

    Args:
        workspace_slug: The workspace slug identifier
        project_id: UUID of the project
        cycle_id: UUID of the cycle

    Returns:
        True if the cycle was unarchived successfully
    """
    client, workspace_slug = get_plane_client_context()
    return client.cycles.unarchive(workspace_slug=workspace_slug, project_id=project_id, cycle_id=cycle_id)
  • plane_mcp/tools/__init__.py:36-36 (registration)
    The tool is registered via `register_cycle_tools(mcp)` call in the `register_tools` function, which is the central registration point for all tools.
    register_cycle_tools(mcp)
  • plane_mcp/tools/cycles.py:20-21 (registration)
    The `register_cycle_tools` function registers all cycle tools (including unarchive_cycle) by decorating them with @mcp.tool() inside the function.
    def register_cycle_tools(mcp: FastMCP) -> None:
    """Register all cycle-related tools with the MCP server."""
  • plane_mcp/tools/cycles.py:17-17 (helper)
    The `get_plane_client_context` helper is imported and used to get the authenticated Plane client and workspace slug needed for the API call.
    from plane_mcp.client import get_plane_client_context

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations, the description should convey behavioral traits. It only states the action without disclosing side effects, required permissions, state expectations, or behavior if the cycle is already unarchived. This is insufficient for a mutation tool.

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 efficient: one sentence with no wasted words. It front-loads the verb. However, it may be too sparse, missing context that would not harm conciseness. Still, it earns a 4 for lack of fluff.

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?

Despite an output schema existing, the description lacks essential context for a mutation tool. It does not explain prerequisites, behavior on unarchiving, or error conditions. For a tool with two required parameters and no annotations, this is under-specified.

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?

Input schema has 100% coverage with descriptions for both parameters ('UUID of the project' and 'UUID of the cycle'). The description adds no additional meaning beyond what the schema provides, so baseline of 3 is appropriate.

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?

The description 'Unarchive a cycle.' clearly states the action (unarchive) and the resource (cycle). It is distinct from sibling tools like archive_cycle, retrieve_cycle, or update_cycle, making its purpose unambiguous.

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 usage guidelines are provided. The description does not indicate when to use this tool, prerequisites (e.g., cycle must be archived), or when not to use it. No alternatives or exclusions are mentioned.

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/goto-software/plane-mcp-server'

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