Yandex Tracker MCP Server

Get Current User

user_get_current

Read-only

Retrieve details about the currently authenticated user in Yandex Tracker. Use this to identify the active user and their account information.

Instructions

Get information about the current authenticated user

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "user_get_current"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`uid`	Yes
`email`	No
`login`	Yes
`display`	No
`external`	No
`lastName`	No
`dismissed`	No
`firstName`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.2Jul 31, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The annotation readOnlyHint:true already discloses the read-only nature, and the description 'Get information' aligns with that. However, the description adds no further behavioral context such as authentication requirements or potential error cases. It is consistent with annotations but does not enrich the agent's understanding beyond them.

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 sentence, front-loaded with the action and resource. There is no wasted wording, and it conveys the essential purpose efficiently.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, output schema present), the description is sufficient. It does not need to explain return values because the output schema covers that. The only minor gap is not explicitly stating that the user is determined by the authentication context, but 'current authenticated user' already implies this.

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, so there is nothing to document. The baseline is 4 per the rubric since no parameter information is needed. The description correctly implies that no user-specific input is required, as it targets the current authenticated user.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get information about the current authenticated user', identifying the specific action (get) and resource (current user). This distinguishes it from siblings like user_get (which fetches a specific user by ID) and users_get_all (which lists users). The verb and resource are precise and unambiguous.

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

Usage Guidelines4/5

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

The description implies usage context: it is for retrieving the currently authenticated user's info. It does not explicitly mention alternatives or exclusions, but the phrase 'current authenticated user' makes it clear when this tool is appropriate compared to user_get or users_search. A slight gap is the lack of explicit 'use this when...' guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server