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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

issue_overview

Get a full overview of an issue: status, comments, links, checklist, and worklog, all in one place for informed decisions.

Instructions

Get a comprehensive overview of an issue including status, comments, links, checklist and worklog.

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>"
    },
    "name": "issue_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_keyYesIssue key (e.g. "DEV-123")
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.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It indicates a read-only operation ('Get') and lists included components, which adds context. However, it does not disclose permissions, potential errors, or any limitations of the aggregate view, so transparency is only partially addressed.

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?

A single, direct sentence that immediately states the tool's purpose and scope. Every word earns its place; it is front-loaded and concise.

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?

The description adequately covers the tool's complexity by listing the five major data types included. Input schema is clear and output schema is present, so return values are handled externally. No significant gaps remain for an aggregate read tool.

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% with both parameters (issue_key and output_format) already documented. The description adds no additional parameter semantics beyond the schema, so baseline 3 is appropriate.

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 (Get) and resource (issue) with a clear scope: comprehensive overview including status, comments, links, checklist, and worklog. It clearly distinguishes from sibling tools like get_issue or list_comments by aggregating multiple aspects.

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: use this when you need a broad overview of an issue rather than calling multiple separate endpoints. However, it does not explicitly name alternatives or state when not to use it, leaving usage guidance only implied.

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