Skip to main content
Glama
alejandroviera

zephyr-squad-server-mcp

add_tests_to_cycle_from_cycle

Adds tests from another cycle as new UNEXECUTED executions in the target cycle. Optionally filter by components, labels, priorities, statuses, or defects.

Instructions

Add tests from another cycle as new UNEXECUTED executions in this cycle.

Tests are sourced from from_cycle_id / from_version_id and can be narrowed by components, labels, priorities, statuses (comma-separated filter strings) and has_defects (bool). project/version accept keys/names or ids (prefer ids to skip a lookup; -1 = Unscheduled). Async: with wait=True (default) polls to completion and returns the final job payload; with wait=False returns {jobProgressToken}.

Important: new executions always start with status UNEXECUTED regardless of the source cycle's results. If you need to carry over the original execution statuses and defect links, use copy_executions_to_cycle instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cycle_idYes
projectYes
versionYes
from_cycle_idYes
from_version_idYes
componentsNo
labelsNo
prioritiesNo
statusesNo
has_defectsNo
assignee_typeNo
folder_idNo
waitNo
timeoutNo
Behavior4/5

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

With no annotations, the description covers key behaviors: new executions always start UNEXECUTED, async behavior with wait, project/version accept keys/names or ids (-1 = Unscheduled). It lacks details on error handling or rate limits but is still thorough.

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 well-structured with paragraphs and bullet points. Each sentence adds value without redundancy. It is concise yet comprehensive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters and no output schema, the description covers usage comprehensively. It explains filters, async mode, and key constraints. A minor gap is the lack of explanation for what 'jobProgressToken' entails, but overall complete.

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

Parameters5/5

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

Schema coverage is 0%, but the description explains all parameters: source, filters (comma-separated strings, boolean), assignee_type, folder_id, wait, timeout. It adds meaning beyond raw schema by clarifying project/version id/name acceptance.

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 tool adds tests from another cycle as new UNEXECUTED executions in this cycle. It specifies the source parameters (from_cycle_id/from_version_id) and distinguishes from the sibling tool copy_executions_to_cycle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use this tool vs. the alternative copy_executions_to_cycle (for carrying over original statuses and defects). It also explains async behavior with wait parameter.

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/alejandroviera/zephyr-squad-server-mcp'

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