Plane MCP

get_cycle

Retrieve details of a single cycle by its unique UUID in a Plane workspace. Provide the cycle_id to get the complete cycle data.

Instructions

Get a single cycle by UUID.

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": {
      "cycle_id": "<cycle_id>"
    },
    "name": "get_cycle"
  }
}

Input Schema

Name	Required	Description	Default
`cycle_id`	Yes
`project_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

B3.4/5.0

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 of disclosing behavioral traits. It only says 'Get a single cycle by UUID' and does not mention side effects, error behavior (e.g., 404 if not found), or return format. While 'Get' implies a read operation, it does not explicitly confirm safety or provide additional context.

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?

The description is a single, concise sentence that front-loads the verb and resource. There is no superfluous text; every word earns its place.

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?

The tool has an output schema and only two parameters (one required), so complexity is low. The description adequately conveys the core action, but it lacks explanation of the optional project_id and does not mention potential error conditions or usage context. It is minimally complete but has clear gaps.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'by UUID' which clarifies cycle_id's format, but it completely ignores the optional project_id parameter. The description adds minimal meaning beyond the schema's bare titles and leaves the purpose of project_id ambiguous.

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 clearly states the verb 'Get' and resource 'cycle', and specifies that it retrieves a single cycle by UUID. This distinguishes it from list_cycles which fetches multiple cycles, and from create_cycle/update_cycle which are mutations.

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?

The description implies usage when you have a UUID and need one specific cycle, but it does not explicitly mention alternatives or when not to use this tool. Sibling tools like list_cycles exist but are not referenced, so the guidance is only implied rather than explicit.

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