Skip to main content
Glama
Sign In
jira-xray-cloud-mcp

jira-xray-cloud-mcp

by netcare-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Xray Get Statuses

xray_get_statuses
Read-onlyIdempotent

Retrieve available test run and step statuses globally or for a specific Jira project to configure Xray workflows and validations.

Instructions

List the test run statuses and step statuses available (globally or for a project).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xray_get_statuses"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoJira project key or id; omit for the global configuration.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the global-vs-project scope distinction, which is useful, but discloses nothing further about behavior. With annotations carrying the load, a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no wasted words; the scope qualifier is compactly parenthesized. Nothing extraneous, though it is terse.

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?

A single optional parameter, full annotation coverage, and an output schema mean little more needs saying. The description covers the essential scope nuance, so an agent can invoke it correctly.

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 coverage is 100% and the single 'project' parameter is fully documented in the schema, including the omit-for-global semantics. The description's mention of 'globally or for a project' restates rather than extends that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (test run statuses and step statuses), which is clear enough to distinguish it from the surrounding test/run CRUD siblings. It does not explicitly name an alternative tool, but the resource is unambiguous.

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 parenthetical '(globally or for a project)' implies the two usage modes, and the schema clarifies that omitting project yields the global configuration. There is no explicit when/when-not guidance or naming of alternatives.

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

Deploy Server

Other Tools