Skip to main content
Glama
aikts

Yandex Tracker MCP

queues_get_all

Retrieve all Yandex Tracker queues accessible to the user, enabling effective project and issue management within the MCP server environment.

Instructions

Find all Yandex Tracker queues available to the user (queue is a project in some sense)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'queues_get_all' tool. Fetches all available Yandex Tracker queues with optional field selection, pagination (all pages if page=None), and filtering by allowed queues.
    @mcp.tool(
        description="Find all Yandex Tracker queues available to the user (queue is a project in some sense)"
    )
    async def queues_get_all(
        ctx: Context[Any, AppContext, Request],
        fields: Annotated[
            list[QueueFieldsEnum] | None,
            Field(
                description="Fields to include in the response. In order to not pollute context window - "
                "select appropriate fields beforehand. Not specifying fields will return all available. "
                "Most of the time one needs key and name only.",
            ),
        ] = None,
        page: Annotated[
            int | None,
            Field(
                description="Page number to return, default is None which means to retrieve all pages. "
                "Specify page number to retrieve a specific page when context limit is reached.",
            ),
        ] = None,
        per_page: PerPageParam = 100,
    ) -> list[Queue]:
        result: list[Queue] = []
    
        find_all = False
        if page is None:
            page = 1
            find_all = True
    
        while find_all:
            queues = await ctx.request_context.lifespan_context.queues.queues_list(
                per_page=per_page,
                page=page,
                auth=get_yandex_auth(ctx),
            )
            if len(queues) == 0:
                break
    
            if settings.tracker_limit_queues:
                queues = [
                    queue
                    for queue in queues
                    if queue.key in set(settings.tracker_limit_queues)
                ]
    
            result.extend(queues)
            if find_all:
                page += 1
    
        if fields is not None:
            set_non_needed_fields_null(result, {f.name for f in fields})
    
        return result
  • Invocation of register_tools which registers the 'queues_get_all' tool (and others) on the FastMCP server instance.
    register_tools(settings, mcp)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('Find all Yandex Tracker queues available to the user') without explaining how it behaves—such as whether it returns all queues at once, if there's pagination, what format the output takes, or any authentication requirements. This leaves significant gaps in understanding the tool's operation.

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 concise and front-loaded, consisting of a single sentence that directly states the tool's purpose, followed by a brief clarifying note. There is no wasted verbiage, and the structure is efficient for understanding the core function quickly.

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 that the tool has zero parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, it lacks details on behavioral aspects like output format or usage context, which could be important for an AI agent to invoke it correctly, especially without annotations. The presence of an output schema reduces the need to describe return values, but more context on operation would improve completeness.

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?

The tool has zero parameters, and the input schema has 100% coverage (though empty). The description appropriately does not discuss parameters, as there are none to explain. This meets the baseline for a parameterless tool without needing to compensate for gaps.

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 tool's purpose: 'Find all Yandex Tracker queues available to the user' with the clarifying note 'queue is a project in some sense'. This provides a specific verb ('Find') and resource ('queues'), though it doesn't explicitly differentiate from sibling tools like 'queue_get_local_fields' or 'queue_get_tags'.

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 when this tool is appropriate compared to other queue-related tools like 'queue_get_local_fields' or 'queue_get_tags', nor does it specify any prerequisites or exclusions for usage.

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