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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

import_comment

Import comments into Yandex Tracker issues while preserving the original creation timestamp and author login.

Instructions

Import a comment with original timestamp and author.

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": {
      "issue_key": "<issue_key>",
      "text": "<text>",
      "created_at": "<created_at>",
      "created_by": "<created_by>"
    },
    "name": "import_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesComment text
issue_keyYesTarget issue key (e.g. "DEV-123")
created_atYesOriginal creation time (ISO 8601, must be within issue's created-updated interval)
created_byYesOriginal author login
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

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of explaining behavior. It mentions preserving original timestamp and author, but omits details about permissions, idempotency, side effects on issue timelines, validation of author existence, or error handling. The schema provides some constraints (e.g., created_at interval), but the description adds little beyond that.

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 that conveys the core purpose with no filler. It is front-loaded and every word contributes to understanding.

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?

The output schema and parameter descriptions provide strong structural context, so the minimal description is acceptable for basic invocation. However, given the presence of the sibling add_comment, more explicit guidance on when to use import_comment would improve completeness. Behavioral gaps (e.g., permissions) also reduce the overall contextual richness.

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%, and the schema already explains each parameter's meaning, including the date constraint. The description adds no new parameter semantics but is not required to compensate given excellent schema coverage.

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 the action ('Import') and the resource ('a comment'), and the phrase 'with original timestamp and author' distinguishes this from sibling tools like add_comment, which creates a new comment with current metadata. The verb and object are immediately understandable.

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 when preserving the original timestamp and author is required, but it does not explicitly state when to choose this over add_comment or mention any exclusions. No alternatives are named, so guidance is only implicit.

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