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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_macro

Create a macro in a Yandex Tracker queue to automate adding comment text and updating fields. Use {{issue.local.<field_key>}} placeholders for dynamic values.

Instructions

Create a macro in a queue.

Tip: use {{issue.local.<field_key>}} to reference local fields in body text.

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": {
      "queue": "<queue>",
      "name": "<name>"
    },
    "name": "create_macro"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoMacro body (comment text to add)
nameYesMacro name
queueYesQueue key (e.g. "DEV")
issue_updateNoFields to update when macro runs (dict)

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 full responsibility for behavioral disclosure. It does not mention side effects, permissions, or whether creation may overwrite existing macros, leaving the agent without important safety context.

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 concise, with the primary purpose stated up front and a single, useful tip that adds practical value. Every sentence earns its place with no redundancy.

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?

For a simple create tool with four parameters and an output schema, the description is adequate but lacks context about prerequisites like queue existence or potential overwrite behavior. The tip partially compensates, but important behavioral context remains missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema describes each parameter at 100% coverage, but the description adds a valuable tip about using {{issue.local.<field_key>}} in the body. This goes beyond the schema's generic body description and helps the agent format the parameter correctly.

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 'Create a macro in a queue' with a specific verb and resource. This distinguishes the create action from sibling tools like update_macro, delete_macro, and get_macro.

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 on when to use this tool versus alternatives. The tip about referencing local fields is useful but pertains to parameter usage, not tool selection criteria.

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