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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

import_link

Import issue relationships with original timestamps and authors. Supply source and target keys, link type, and creation details to preserve historical accuracy.

Instructions

Import a link between issues with original timestamp.

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>",
      "relationship": "<relationship>",
      "target": "<target>",
      "created_at": "<created_at>",
      "created_by": "<created_by>"
    },
    "name": "import_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesTarget issue key
issue_keyYesSource issue key
created_atYesOriginal creation time (ISO 8601, must be within both issues' intervals)
created_byYesOriginal author login
relationshipYesLink type (e.g. "relates", "depends on")

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description is the only behavioral disclosure, yet it only mentions the timestamp attribute. It does not disclose whether the import is additive, idempotent, permission-scoped, or how conflicts or duplicate links are handled.

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 with no filler, and the key differentiator ('original timestamp') is front-loaded. It is maximally concise, although this brevity trades off behavioral detail.

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

Completeness2/5

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

With 5 required parameters, zero annotations, and no usage context, the single-sentence description is insufficient for an import/mutation tool. It omits validation semantics, conflict handling, and return behavior; the existence of an output schema does not compensate for the missing operational context.

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 covers 100% of parameters with meaningful descriptions (source/target keys, relationship, created_at, created_by), so the schema carries the semantic burden. The description adds no parameter-level nuance beyond saying 'original timestamp'.

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 uses a specific verb ('Import') and resource ('link between issues') plus a distinguishing constraint ('original timestamp'). This clearly differentiates it from the sibling tool 'link_issues', which presumably creates a link with the current timestamp.

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?

No explicit when-to-use or alternative guidance is provided. The word 'Import' and 'original timestamp' imply a migration/backfill context, but the description does not contrast with link_issues, list_links, or other import tools, nor does it state prerequisites or exclusions.

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