Skip to main content
Glama
aikts

Yandex Tracker MCP

user_get_current

Retrieve details about the currently authenticated user in Yandex Tracker, enabling access to user-specific information and role validation within the platform.

Instructions

Get information about the current authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes
emailNo
loginYes
displayNo
externalNo
lastNameNo
dismissedNo
firstNameNo

Implementation Reference

  • MCP tool handler for 'user_get_current'. Registers the tool and implements the logic by proxying to the underlying users service to fetch the current authenticated user.
    async def user_get_current(
        ctx: Context[Any, AppContext],
    ) -> User:
        user = await ctx.request_context.lifespan_context.users.user_get_current(
            auth=get_yandex_auth(ctx),
        )
        return user
  • Core implementation of user_get_current in the Yandex Tracker client, making an HTTP GET request to the '/v3/myself' endpoint to retrieve the current user data.
    async def user_get_current(self, *, auth: YandexAuth | None = None) -> User:
        async with self._session.get(
            "v3/myself", headers=await self._build_headers(auth)
        ) as response:
            response.raise_for_status()
            return User.model_validate_json(await response.read())
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. While 'Get information' implies a read operation, it doesn't specify what information is returned, whether authentication is required (though implied), or any rate limits or constraints. The description is minimal and lacks important behavioral context.

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 any wasted words. It's appropriately sized for a simple tool with no parameters and gets straight to the point.

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 an output schema (which should document return values) and no parameters, the description is reasonably complete for its simple purpose. However, for a user information tool in what appears to be a Jira/issue tracking context, more context about what user information is retrieved would be helpful despite the output schema.

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 already fully documents the parameter situation. The description appropriately doesn't mention parameters since none exist, which is correct for this case. Baseline for 0 parameters is 4.

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 information') and resource ('current authenticated user'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling 'user_get' tool, which appears to be a similar user retrieval function but for different targets.

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

Usage Guidelines3/5

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

The description implies usage context through 'current authenticated user' - suggesting this tool should be used when you need information about the user making the API call. However, it provides no explicit guidance about when to use this versus the sibling 'user_get' tool or other user-related operations.

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