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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_filter

Create a saved filter in Yandex Tracker to reuse issue queries and filter conditions. Specify a name and either a query string or filter dict.

Instructions

Create a saved filter.

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

Input Schema

NameRequiredDescriptionDefault
nameYesFilter name
queryNoQuery string (e.g. 'Queue: DEV Resolution: empty()')
filterNoFilter as dict (e.g. {"queue": "DEV", "status": "open"})

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

C2.4/5.0
Behavior1/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. It merely states 'Create a saved filter' with no mention of side effects, idempotency, potential overwrites, permission requirements, or what happens on duplicate names. This is essentially a tautology of the tool name and provides no behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, which makes it concise in word count, but it is under-specified rather than efficiently informative. It is essentially just an expansion of the tool name and fails to include any contextual or behavioral information that would justify its brevity.

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?

Given the tool has three parameters (one required), an output schema, and no annotations, the description is too minimal to provide complete context. It does not explain how to use the filter versus query parameters, when to omit them, or what the created filter is used for. The output schema covers return values, but the description still leaves significant gaps in understanding the tool's behavior.

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 has 100% coverage with descriptions for all three parameters ('name', 'query', and 'filter'), so the description adds no additional semantic value. Since the schema already documents parameter meanings, the baseline score of 3 is appropriate; the description neither enhances nor detracts from parameter understanding.

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 'Create a saved filter.' clearly states the action (create) and resource (saved filter), which differentiates it from sibling tools like get_filter and update_filter. However, it is minimal and does not explicitly highlight how it differs from related operations beyond the verb itself.

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?

The description provides no guidance on when to use this tool versus alternatives such as update_filter or get_filter. It does not mention any prerequisites, constraints, or the choice between query and filter parameters, leaving the agent to infer usage from the schema alone.

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