Skip to main content
Glama
aikts

Yandex Tracker MCP

queue_get_versions

Retrieve all versions associated with a specific Yandex Tracker queue by providing the Queue ID. Facilitates issue management and version tracking within projects.

Instructions

Get all versions for a specific Yandex Tracker queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queue_idYesQueue (Project ID) to search in, like 'SOMEPROJECT'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'queue_get_versions' tool. It checks if the queue is allowed, then calls the underlying tracker API to fetch versions for the given queue_id.
    @mcp.tool(description="Get all versions for a specific Yandex Tracker queue")
    async def queue_get_versions(
        ctx: Context[Any, AppContext],
        queue_id: QueueID,
    ) -> list[QueueVersion]:
        if (
            settings.tracker_limit_queues
            and queue_id not in settings.tracker_limit_queues
        ):
            raise TrackerError(f"Queue `{queue_id}` not found or not allowed.")
    
        versions = (
            await ctx.request_context.lifespan_context.queues.queues_get_versions(
                queue_id,
                auth=get_yandex_auth(ctx),
            )
        )
        return versions
  • The @mcp.tool decorator registers the queue_get_versions function as an MCP tool.
    @mcp.tool(description="Get all versions for a specific Yandex Tracker queue")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides minimal information. It states it 'gets' data (implying read-only), but doesn't mention authentication requirements, rate limits, pagination behavior, error conditions, or what constitutes a 'version' in this context. For a tool with no annotation coverage, this represents significant behavioral gaps.

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 a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information. Every word earns its place in this concise formulation.

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

Completeness3/5

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

Given the tool has an output schema (which handles return values) and 100% schema description coverage for its single parameter, the description is minimally adequate. However, for a tool with no annotations, it should provide more behavioral context about what 'versions' means in this system, potential constraints, or typical use cases to be truly complete.

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?

The schema has 100% description coverage, with the single parameter 'queue_id' well-documented in the schema itself. The description doesn't add any parameter semantics beyond what's already in the schema - it mentions 'specific Yandex Tracker queue' which aligns with but doesn't enhance the schema's 'Queue (Project ID) to search in' description. This meets the baseline for high schema coverage.

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?

The description clearly states the action ('Get all versions') and target resource ('for a specific Yandex Tracker queue'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings like 'queue_get_local_fields' or 'queue_get_tags' which also retrieve queue-specific metadata, leaving room for improvement in sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for retrieving queue versions, or how this differs from other queue-related tools like 'queues_get_all' or issue-focused tools. This lack of usage context leaves the agent without direction on appropriate application.

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

Related 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