zephyr-squad-server-mcp

assign_execution

Assign a Jira test execution to a user by specifying the execution ID and assignee account ID.

Instructions

Assign an execution to a user.

assignee is a Jira username/account id. (execution_id is the schedule id from list_executions.) Returns the API's (empty) acknowledgement.

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": {
      "execution_id": "<execution_id>",
      "assignee": "<assignee>"
    },
    "name": "assign_execution"
  }
}

Input Schema

Name	Required	Description	Default
`execution_id`	Yes
`assignee`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Discloses return value (empty acknowledgement) and implies mutation, but without annotations it could cover permissions or side effects more thoroughly.

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 efficient sentences with no redundancy; front-loads main action and provides parameter context concisely.

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?

Sufficient for a simple assignment tool given sibling context; mentions return type but could include error handling or constraints.

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?

Adds essential meaning beyond schema: clarifies assignee format and execution_id source, compensating for 0% schema coverage.

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 'Assign an execution to a user' with specific verb and resource. It distinguishes from siblings by focusing on assignment, not creation or update.

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

Usage Guidelines4/5

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

Provides guidance on parameter sources (Jira username, schedule ID from list_executions), but lacks explicit when-to-use or alternatives compared to similar tools like assign_execution vs. update_execution.

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