zephyr-squad-server-mcp

get_cycle

Retrieve details of a test cycle by its numeric ID. Use -1 to fetch the Ad hoc cycle.

Instructions

Get a single test cycle's details by its numeric id.

Passing -1 returns the hardcoded Ad hoc cycle.

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It only mentions parameter behavior and special value -1, but omits return structure (what 'details' are), error handling, or idempotency. For a read operation, more context on safety and response is needed.

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?

Two concise sentences with no filler. First sentence states core purpose, second adds critical special case. 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?

Adequate for a simple get tool given one required parameter, but lacks output structure, error scenarios, and explicit read-only guarantee. With no output schema or annotations, additional detail on return values would improve completeness.

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

Parameters4/5

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

Schema coverage is 0%, but description adds significant value by explaining 'numeric id' and noting the special '-1' value for Ad hoc cycle, which is not evident from the schema alone.

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?

Description clearly states verb ('Get') and resource ('a single test cycle's details') with specificity ('by its numeric id'). Includes a special case note about '-1' for Ad hoc cycle, distinguishing itself from siblings like list_cycles or update_cycle.

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?

Implies use when a specific cycle id is known, but no explicit guidance on when to use alternatives (e.g., list_cycles for listing, or update_cycle for modifications). No when-not or prerequisite conditions mentioned.

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