Skip to main content
Glama
goto-software

plane-mcp-server

retrieve_cycle

Fetch details of a specific cycle by providing its UUID and the project UUID.

Instructions

Retrieve a cycle by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
cycle_idYesUUID of the cycle

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
total_issuesNo
cancelled_issuesNo
completed_issuesNo
started_issuesNo
unstarted_issuesNo
backlog_issuesNo
total_estimatesNo
completed_estimatesNo
started_estimatesNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
start_dateNo
end_dateNo
view_propsNo
sort_orderNo
external_sourceNo
external_idNo
progress_snapshotNo
archived_atNo
logo_propsNo
timezoneNo
versionNo
created_byNo
updated_byNo
projectNo
workspaceNo
owned_byNo
Behavior2/5

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

Without annotations, the description should disclose behavioral traits. It only states 'Retrieve', implying read-only, but does not mention potential errors, permissions, or side effects.

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 a single concise sentence with no fluff, but it could be slightly more informative without becoming verbose.

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 existence of an output schema, the description does not need to explain return values. However, it lacks usage and behavioral context, making it minimally adequate.

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?

The input schema already provides full descriptions for both parameters ('UUID of the project', 'UUID of the cycle'), so the description adds no additional meaning. Baseline 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 clearly states the action ('Retrieve'), the resource ('a cycle'), and the scope ('by ID'), making it specific and distinguishable from siblings like 'list_cycles' which retrieves multiple cycles.

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 guidance is provided on when to use this tool versus alternatives (e.g., list_cycles), nor any preconditions or when not to use it.

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