JIRA MCP Server

xray_get_test_steps

Get test steps for an Xray test case by issue key. Returns step details including ID, data, expected result, and attachments.

Instructions

Recupera gli step di un Test Xray tramite la chiave issue (es. PROJ-123). Restituisce id, step, dati, risultato atteso e allegati per ogni step.

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": {
      "issueKey": "<issueKey>"
    },
    "name": "xray_get_test_steps"
  }
}

Input Schema

Name	Required	Description	Default
`issueKey`	Yes	Chiave della issue Test Xray (es. PROJ-123)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 8, 2026

TDQS

A4.2/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 full burden. It discloses the return fields (id, step, dati, risultato atteso, allegati) and implies a read-only operation. No contradictions.

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 two sentences, front-loads the purpose, and contains no extraneous information.

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?

For a simple retrieval tool with one parameter and no output schema, the description adequately covers what the tool does and what it returns. It lacks error or limit information but is appropriate for the complexity.

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?

With 100% schema description coverage, the description adds minimal value beyond the schema (example issue key format). It repeats 'chiave issue' but does not provide additional syntax or constraints.

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 ('Recupera') and resource ('step di un Test Xray tramite la chiave issue'), and it uniquely identifies this tool among siblings (only Xray tool, others are Confluence/Jira).

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?

The description explicitly mentions when to use the tool (given an issue key) and relates it to Xray Test steps. However, it does not specify when not to use it or provide alternatives, though sibling tools are distinct.

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