Skip to main content
Glama
aikts

Yandex Tracker MCP

users_get_all

Retrieve details of all user accounts within an organization using pagination parameters to manage large datasets effectively. Integrates with Yandex Tracker MCP for streamlined user data access.

Instructions

Get information about user accounts registered in the organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to return, default is 1
per_pageNoThe number of items per page. May be decreased if results exceed context window. If there is a change in per_page argument - retrieval must be started over with page = 1, as the paging could have changed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for 'users_get_all' tool, decorated with @mcp.tool for registration. Fetches paginated list of users from Yandex Tracker using the tracker client.
    @mcp.tool(
        description="Get information about user accounts registered in the organization"
    )
    async def users_get_all(
        ctx: Context[Any, AppContext],
        page: PageParam = 1,
        per_page: PerPageParam = 50,
    ) -> list[User]:
        users = await ctx.request_context.lifespan_context.users.users_list(
            per_page=per_page,
            page=page,
            auth=get_yandex_auth(ctx),
        )
        return users
  • Input schema definitions for pagination parameters (PageParam, PerPageParam) used by the users_get_all tool.
    PageParam = Annotated[
        int,
        Field(
            description="Page number to return, default is 1",
            ge=1,
        ),
    ]
    
    PerPageParam = Annotated[
        int,
        Field(
            description="The number of items per page. May be decreased if results exceed context window. "
            "If there is a change in per_page argument - retrieval must be started over with page = 1, "
            "as the paging could have changed.",
            ge=1,
        ),
    ]
  • Invocation of register_tools which registers the users_get_all tool (along with others) on the MCP server instance.
    register_tools(settings, mcp)
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. It states this is a 'Get' operation but doesn't mention pagination behavior (implied by parameters), rate limits, authentication requirements, or what specific user information is returned. The description provides basic intent but lacks operational context needed for effective tool selection.

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 without unnecessary words. It's appropriately sized for a list/retrieval operation and front-loads the essential information. Every word earns its place in conveying the core functionality.

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 this is a read-only list operation with 2 documented parameters and an output schema (which handles return values), the description provides adequate context. The combination of clear purpose, complete parameter documentation in schema, and output schema coverage makes this reasonably complete for a paginated list tool, though behavioral context could be enhanced.

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%, providing complete documentation for both pagination parameters. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in description, which applies here.

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 'information about user accounts registered in the organization', making the purpose immediately understandable. It distinguishes from sibling 'user_get' which likely retrieves a single user, though this distinction isn't explicitly stated. The description is specific but doesn't fully differentiate from all possible alternatives.

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 about when to use this tool versus alternatives like 'user_get' or 'user_get_current'. The description implies it retrieves all users in the organization, but doesn't specify use cases, prerequisites, or limitations compared to sibling tools. The agent must infer usage context from the tool name 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