Skip to main content
Glama
aikts

Yandex Tracker MCP

by aikts
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

issue_get_url

Retrieve the URL of a Yandex Tracker issue by providing its ID in the format '-'. Access and manage issue details directly through the Yandex Tracker MCP server.

Instructions

Get a Yandex Tracker issue url by its id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYesIssue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • mcp_tracker/mcp/tools.py:202-206 (handler)
    The core handler function for the 'issue_get_url' tool. It takes an issue_id and returns the direct URL to the Yandex Tracker issue.
    @mcp.tool(description="Get a Yandex Tracker issue url by its id")
async def issue_get_url(
    issue_id: IssueID,
) -> str:
    return f"https://tracker.yandex.ru/{issue_id}"
  • mcp_tracker/mcp/params.py:23-26 (schema)
    Pydantic schema definition for the input parameter 'issue_id' used by the tool.
    IssueID = Annotated[
    str,
    Field(description="Issue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'"),
]
  • mcp_tracker/mcp/server.py:166-166 (registration)
    Invocation of register_tools function, which defines and registers the issue_get_url tool (among others) with the MCP server instance.
    register_tools(settings, mcp)

Tool Definition Quality

B3.1/5.0
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. It states it 'Get[s]' a URL, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, rate limits, error handling, or what the output looks like. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 directly states the tool's purpose with zero waste. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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's low complexity (one parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and incomplete behavioral transparency, it doesn't fully compensate for the lack of structured safety or usage context, leaving room for improvement.

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?

Schema description coverage is 100%, with the parameter 'issue_id' fully documented in the schema as 'Issue ID in the format '<project>-<id>', like 'SOMEPROJECT-1''. The description adds no additional meaning beyond what the schema provides, such as examples or context. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the resource 'a Yandex Tracker issue url by its id', making the purpose specific and understandable. It distinguishes from siblings like 'issue_get' (which likely retrieves full issue data) by focusing on just the URL. However, it doesn't explicitly contrast with other siblings, so it's not a perfect 5.

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 scenarios where only the URL is needed versus full issue data (from 'issue_get'), nor does it specify prerequisites or exclusions. The agent must infer usage from the name and description alone.

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