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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_bulk_status

Check the current status of a bulk operation to monitor its progress and confirm completion.

Instructions

Check the status of a bulk operation.

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": {
      "bulk_change_id": "<bulk_change_id>"
    },
    "name": "get_bulk_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_formatNoResponse format: "text" (default, markdown) or "json"text
bulk_change_idYesBulk operation ID (from bulk_update/bulk_move/bulk_transition)

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 the full burden of behavioral disclosure, but it only states the basic action. It does not mention that this is a read-only operation, how status is represented, possible outcomes, or error conditions. The lack of additional context leaves the agent uncertain about the operation's behavior beyond the minimal action.

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, direct sentence with no redundant information. It is appropriately concise and front-loaded, making it easy for an agent to quickly understand the tool's core function.

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 tool's simplicity and the presence of an output schema, the description is minimally viable. However, it lacks context about how this tool fits into the bulk operation workflow, such as when to use it after bulk_update/bulk_move/bulk_transition. The absence of usage context relative to the large sibling set makes it less complete than ideal.

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 description adds no parameter information, but the input schema has 100% description coverage. Both 'bulk_change_id' and 'output_format' have clear, self-explanatory descriptions in the schema, so the baseline of 3 applies. The description does not need to compensate for schema gaps.

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 'Check the status of a bulk operation' clearly identifies the action (check) and the resource (status of a bulk operation). It distinguishes itself from siblings like get_bulk_failed_issues, which focuses on failed issues rather than overall operation status. The purpose is specific and unambiguous.

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 explicit guidance is provided on when to use this tool versus alternatives. The schema parameter description mentions 'from bulk_update/bulk_move/bulk_transition', which hints at usage context, but the description itself offers no such direction. There is no discussion of prerequisites, alternatives, or exclusion 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