zephyr-squad-server-mcp

create_folder

Create a folder under a specified test cycle in Zephyr for Jira, using cycle ID, project, version, and folder name. Returns folder ID and response message.

Instructions

Create a folder under a cycle.

project/version accept keys/names or ids (prefer ids when you have them, to skip a lookup; -1 = Unscheduled). Returns {id, responseMessage}.

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": "<name>",
      "project": "<project>",
      "version": "<version>"
    },
    "name": "create_folder"
  }
}

Input Schema

Name	Required	Description	Default
`cycle_id`	Yes
`name`	Yes
`project`	Yes
`version`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A4/5.0

Behavior4/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. It discloses the return format ('{id, responseMessage}') and explains how 'project' and 'version' parameters are interpreted. It does not mention permissions, error scenarios, or constraints like unique folder names, but it is adequate for a simple creation tool.

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 extremely concise: two sentences, front-loading the main purpose and then providing parameter hints and return type. Every sentence adds value.

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 the tool has 5 parameters (4 required), no output schema, and no annotations, the description covers the essential aspects: purpose, return format, and parameter nuances for key fields. It lacks details on the 'description' parameter and constraints like uniqueness, but it is largely complete for a straightforward folder creation tool.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning for 'project' and 'version' (accept keys/names/ids, prefer ids, -1 = Unscheduled). However, it does not explain 'cycle_id', 'name', or 'description' beyond their names and types in the schema.

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 ('Create a folder') and the context ('under a cycle'). This distinguishes it from sibling tools like 'create_cycle' (creates cycles) and 'update_folder' (updates folders).

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 provides context (folder creation under a cycle) and gives usage hints for the 'project' and 'version' parameters (prefer ids, use -1 for Unscheduled). However, it does not explicitly state when to use this tool versus alternatives or mention any prerequisites or exclusions.

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