Skip to main content
Glama
Sign In
ya-tracker-mcp

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

transition_issue

Change an issue's status by applying a specified transition. Optionally add a comment to record context.

Instructions

Execute a status transition on an issue.

Use list_transitions first to get available 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": {
      "issue_key": "<issue_key>",
      "transition_id": "<transition_id>"
    },
    "name": "transition_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional comment for the transition
issue_keyYesIssue key (e.g. "DEV-123")
output_formatNoResponse format: "text" (default, markdown) or "json"text
transition_idYesTransition ID (from list_transitions)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It indicates the action is state-changing but does not mention permissions, failure modes, side effects, or response contents. The prerequisite hint is helpful but insufficient for full transparency.

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 short, purposeful sentences: the first states the action, the second provides the essential prerequisite. No filler, repetition, or unnecessary detail.

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 straightforward transition tool with full parameter schema coverage and an output schema, the description supplies the crucial prerequisite step. It could mention exclusions like bulk_transition for multiple issues, but overall it is sufficient for an agent to select and invoke the tool 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 each parameter has a description. The description reinforces that transition_id comes from list_transitions but adds no significant semantic beyond the schema, matching the baseline for full 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 a specific action ('Execute a status transition') on a specific resource ('an issue'), distinguishing it from sibling tools like update_issue, move_issue, and bulk_transition. The verb+resource structure is explicit and unambiguous.

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?

It provides a clear procedural instruction: call list_transitions first to obtain the available transition IDs. This tells the agent how to prepare for using the tool, though it does not explicitly contrast with alternative bulk transition or move tools.

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