Skip to main content
Glama
aikts

Yandex Tracker MCP

get_priorities

Retrieve all available issue priorities in Yandex Tracker to ensure accurate task categorization and workflow management.

Instructions

Get all priorities available in Yandex Tracker that can be used in issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary MCP tool handler for 'get_priorities'. It is decorated with @mcp.tool and delegates to the underlying fields client protocol.
    @mcp.tool(
        description="Get all priorities available in Yandex Tracker that can be used in issues"
    )
    async def get_priorities(
        ctx: Context[Any, AppContext],
    ) -> list[Priority]:
        priorities = await ctx.request_context.lifespan_context.fields.get_priorities(
            auth=get_yandex_auth(ctx),
        )
        return priorities
  • Registration of tools including 'get_priorities' via register_tools call after creating the FastMCP server instance.
    mcp = create_mcp_server()
    register_resources(settings, mcp)
    register_tools(settings, mcp)
  • Concrete implementation of get_priorities in the TrackerClient class, which makes an HTTP GET request to the Yandex Tracker '/v3/priorities' API endpoint and parses the response.
    async def get_priorities(self, *, auth: YandexAuth | None = None) -> list[Priority]:
        async with self._session.get(
            "v3/priorities", headers=await self._build_headers(auth)
        ) as response:
            response.raise_for_status()
            return PriorityList.model_validate_json(await response.read()).root
  • Protocol (abstract method) definition for get_priorities in GlobalDataProtocol, implemented by client wrappers.
    async def get_priorities(
        self, *, auth: YandexAuth | None = None
    ) -> list[Priority]: ...
  • Caching wrapper for get_priorities that delegates to the original implementation with aiocache.
    async def get_priorities(
        self, *, auth: YandexAuth | None = None
    ) -> list[Priority]:
        return await self._original.get_priorities(auth=auth)
Behavior2/5

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

With no annotations, the description carries full burden but only states what the tool does, not behavioral traits like whether it's read-only, requires authentication, has rate limits, or returns paginated results. It lacks details on output format or error handling, leaving gaps for a tool with zero parameters.

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 with no wasted words, front-loading the core action and resource. It's appropriately sized for a simple retrieval tool with no parameters.

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 0 parameters, an output schema exists, and no annotations, the description is minimally adequate but incomplete. It covers the purpose but lacks behavioral context and usage guidelines, making it functional but not fully helpful for an agent.

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 0 parameters with 100% schema description coverage, so the schema fully documents inputs. The description doesn't add parameter details, which is acceptable here, but it implies the output is priorities for issues, adding slight context beyond the empty schema.

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 verb ('Get') and resource ('all priorities available in Yandex Tracker'), specifying they are for use in issues. It distinguishes from siblings like get_statuses or get_issue_types by focusing on priorities, though it doesn't explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives. It mentions priorities 'can be used in issues,' which implies a context but doesn't specify prerequisites, timing, or exclusions relative to sibling tools like issue_get or issues_find.

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