Skip to main content
Glama
aikts

Yandex Tracker MCP

Close Issue

issue_close

Close a Yandex Tracker issue by automatically applying the appropriate transition to a done status with a specified resolution. Before using, retrieve the issue type and queue metadata to choose a valid resolution.

Instructions

Close a Yandex Tracker issue with a resolution. This is a convenience tool that automatically finds a transition to a 'done' status and executes it with the specified resolution. IMPORTANT: Before closing, you MUST: 1) Call issue_get to retrieve the issue's type field. 2) Call queue_get_metadata with expand=['issueTypesConfig'] to get available resolutions. 3) Choose a resolution from the issueTypesConfig entry matching the issue's type - each issue type has its own set of valid resolutions. Returns a list of transitions available for the issue in its new (closed) status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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').
fieldsNoOptional dictionary of additional fields to set during the transition. Common fields include 'resolution' (e.g., 'fixed', 'wontFix') for closing issues, 'assignee' for reassigning, etc.
commentNoOptional comment to add when closing the issue.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations only indicate readOnlyHint: false (write operation). The description adds that the tool automatically finds the correct transition, requires specific pre-conditions, and returns the list of transitions in the new status, fully compensating for minimal annotations.

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?

The description is well-structured, front-loading the purpose and key prerequisites in bold. It is slightly verbose (10 sentences) but each sentence adds necessary information, making it effective.

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?

Given the output schema exists (context reads true), the description covers all necessary context: purpose, pre-conditions, parameter constraints, return value (list of transitions), and special behavior (convenience auto-find). It fully equips the agent to use the tool correctly.

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% with parameter descriptions. The description enhances by specifying resolution_id must come from get_resolutions tool and explaining the fields parameter's common uses. While schema already defines types, the added context is valuable.

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 closes a Yandex Tracker issue with a resolution, positioning it as a convenience tool that finds a 'done' transition. This distinguishes it from sibling tools like issue_execute_transition, which handles general transitions.

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?

The description provides explicit prerequisites: must retrieve issue type via issue_get, get queue metadata with issueTypesConfig, and choose a valid resolution. This tells the agent when and how to use the tool, with clear steps and alternatives implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aikts/yandex-tracker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server