Skip to main content
Glama
Sign In
ya-tracker-mcp

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_user

Retrieve detailed information about a specific user by login or UID. Supports text or JSON output formats.

Instructions

Get info about a specific user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser login or UID
output_formatNoResponse format: "text" (default, markdown) or "json"text

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only says 'Get info,' implying a read operation, but it does not mention any permissions required, data sensitivity, or response structure. This lack of behavioral context is a significant gap, even for a simple getter.

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, concise sentence that directly states the tool's purpose without redundant details. It is appropriately sized for the tool's simplicity and front-loaded with the key action and target.

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 low complexity (2 params, one required) and presence of an output schema, the description is minimally viable. However, it lacks usage guidance and behavioral transparency, which are especially important because no annotations exist. The description is adequate but leaves clear gaps for an AI agent deciding between this and similar user-related tools.

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?

The input schema provides complete descriptions for both parameters (user_id and output_format) with 100% coverage. The description adds no extra meaning beyond what the schema already states, so it meets the baseline for well-documented parameters but does not enhance understanding.

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 'Get info about a specific user' uses a clear verb ('Get') and resource ('a specific user'), making the purpose immediately understandable. It distinguishes from broader list tools by emphasizing 'specific user,' but it does not explicitly differentiate from siblings like get_myself or list_users, so it falls short of a 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 neither states explicit use cases nor mentions when not to use it, despite a rich set of sibling tools (e.g., get_myself, list_users, get_team_member) that could easily be confused with this one.

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

Deploy Server

Other Tools