Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Tracker entities

tracker_entities_search
Read-onlyIdempotent

Search Yandex 360 Tracker entities by type, name substring, filters, and sort order to find matching projects, portfolios, goals, or reports.

Instructions

Entities of a given type that match a name substring and a filter, sorted server-side.

Returns a flat list of entities. body.input matches part of the name, body.filter is a field → value object (author, status, followers, …), body.orderBy with body.orderAsc sorts, and body.rootOnly keeps the entities with no parent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoWhat to find: name substring, filter, sort order; omit for all.
fieldsNoComma-separated extra fields to include.
entity_typeYesEntity type: ``project``, ``portfolio``, ``goal`` or ``report`` (issue reports).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.122.1
    • addedInput schema / properties / body
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "description": "Typed request body for ``POST /entities/{type}/_search``.",
+      "properties": {
+        "filter": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Field name → value the entities must have."
+        },
+        "input": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Substring to find in the entity name."
+        },
+        "orderAsc": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Sort ascending; needs ``order_by``."
+        },
+        "orderBy": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Key of the field to sort by."
+        },
+        "rootOnly": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Only entities with no parent."
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "What to find: name substring, filter, sort order; omit for all."
+}
    • removedInput schema / properties / input_text
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Substring to match in the entity name."
-}
    • removedInput schema / properties / order_by
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Field key to sort the results by."
-}
  2. First observedv0.67.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so safety is covered. The description adds return-shape context ('flat list of entities') and that sorting is server-side, which is useful, but it does not cover result limits, pagination, or permission requirements.

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

Conciseness4/5

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

Two compact sentences, front-loaded with the core purpose and followed by parameter explanation. Minor inconsistency between 'body.orderBy' in prose and 'order_by' referenced in the schema, but no wasted sentences.

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?

For a read-only search tool with no output schema, the description supplies the essentials an agent needs: what it returns (flat list), what it filters on, and how sorting works. Missing only edge-case behavior (limits, defaults when body is omitted) which the schema partially covers.

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?

Schema coverage is 100%, so baseline is 3, but the description adds genuine value: concrete filter examples (author, status, followers), the interaction of body.orderBy with body.orderAsc, and the meaning of rootOnly (no parent). It slightly exceeds the schema's own per-field descriptions.

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 definition states a specific verb (search) and resource (Tracker entities of a given type) and names the matching criteria (name substring + filter) and server-side sorting. It distinguishes itself from tracker_entities_get/create, though it does not explicitly contrast with neighbors like tracker_entities_get or tracker_issues_search.

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?

Usage is implied by the description of matching behavior (substring, filter, rootOnly) and the schema note that body can be omitted for all results. There is no explicit when-to-use guidance or naming of an alternative sibling (e.g., tracker_entities_get for a single entity), so an agent must infer the selection.

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