Skip to main content
Glama

jira_get_transitions

Lists available workflow transitions for a Jira issue and returns valid transition IDs. Use it before changing status to identify the correct transition.

Instructions

List the available workflow transitions (status changes) for an issue. Returns transition IDs and names like "Start Progress", "Resolve", "Close". The available transitions depend on the issue's current status and your workflow configuration. ALWAYS call this before jira_transition_issue to get valid transition IDs.

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": "jira_get_transitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesIssue key to check transitions for (e.g., KP-123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does part of it well: the verb 'List' signals a read, it discloses that results vary by current status and workflow configuration, and it describes the return payload (IDs plus names). It stops short of stating permission/auth requirements or whether the result set is ever empty, which for a status-dependent read would be useful.

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?

Four short sentences, front-loaded with the definition, then the return shape, then the variability caveat, then the mandatory ordering rule. Every sentence carries distinct information and the imperative call-to-action lands last where it is most salient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

One required string parameter, no output schema, no annotations — a lightweight tool that the description fully covers. It supplies what the structured fields cannot: the return format, the status-dependence of results, and the required call sequence. Nothing an agent needs to invoke it correctly is missing.

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 100%, so issueKey plus its KP-123 example is already documented in the schema, and the description adds no further syntax or format detail. The one context item it contributes is that the issue's current status shapes the output, which is about results rather than the parameter. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List the available workflow transitions (status changes) for an issue') and clarifies the domain term 'transitions' with plain-language 'status changes'. The parenthetical examples ('Start Progress', 'Resolve', 'Close') and the explicit contrast with jira_transition_issue make it unambiguous against the closest sibling.

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

Usage Guidelines5/5

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

Gives a hard precondition: 'ALWAYS call this before jira_transition_issue to get valid transition IDs.' The named alternative and the ordering constraint leave nothing to inference, and the dependency on current status tells the agent results are not cacheable across states.

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