Skip to main content
Glama
Sign In
Yandex Tracker MCP

Yandex Tracker MCP

by aikts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Close Issue

issue_close

Close a Yandex Tracker issue by specifying a resolution and moving it to done status, with optional comment and field updates.

Instructions

Close a Yandex Tracker issue with a resolution: finds a transition to a 'done' status and executes it. The resolution has to be one the issue's type allows - read the type with issue_get, then call queue_get_metadata with expand=['issueTypesConfig'] for the resolutions of that type. Returns the transitions available in the new (closed) status.

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_id": "<issue_id>",
      "resolution_id": "<resolution_id>"
    },
    "name": "issue_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional dictionary of additional fields to set during the transition (e.g. 'assignee' for reassigning). Do NOT set 'resolution' here - use the dedicated resolution_id parameter instead.
commentNoOptional comment to add when closing the issue.
issue_idYesIssue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
resolution_idYesThe resolution ID to set when closing the issue. Must be one of the IDs returned by get_resolutions tool (e.g., 'fixed', 'wontFix', 'duplicate').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / fields / description
      Previous value: -"Optional dictionary of additional fields to set during the transition. Common fields include 'resolution' (e.g., 'fixed', 'wontFix') for closing issues, 'assignee' for reassigning, etc."New value: +"Optional dictionary of additional fields to set during the transition (e.g. 'assignee' for reassigning). Do NOT set 'resolution' here - use the dedicated resolution_id parameter instead."
  2. Addedv0.6.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only state readOnlyHint=false, so the description carries the behavioral burden. It discloses that the tool mutates state by executing a transition, that it targets 'done' status, that resolution must be valid for the issue type, and that it returns the transitions available in the closed status. This is meaningful behavioral context beyond the annotation.

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 compact: two sentences that lead with the core action and resolution constraint, then state the return value. Every sentence carries needed information without repetition or filler.

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?

The definition covers the operation, resolution-selection process, and return value, which is strong for a focused tool with a full schema and output schema. It could be slightly more complete by mentioning what happens if no 'done' transition is available, but this is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds important semantic value for resolution_id by explaining it must be allowed by the issue's type and how to discover the allowed values via issue_get and queue_get_metadata. It does not add detail for fields or comment, but the schema already describes those clearly.

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 tool's specific action: closing a Yandex Tracker issue by finding and executing a transition to a 'done' status. It names the exact resource and operation, and the 'finds a transition' detail helps distinguish it from a generic transition tool like issue_execute_transition.

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 gives explicit procedural guidance: read the issue type, call queue_get_metadata, then provide a resolution allowed by that type. It does not explicitly name alternative tools like issue_execute_transition or state when not to use this tool, but the context and specialized purpose make the intended use clear.

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