Skip to main content
Glama
A1 Yandex KIT MCP

A1 Yandex KIT MCP

Search KIT API operations

search_operations
Read-only

Search all 179 Yandex KIT API operations by keyword across operationId, path, tag, and Russian summary. Find a matching operation, then inspect its schema to execute it.

Instructions

Search the full catalog of all 179 Yandex KIT API operations by keyword. Matches operationId, URL path, tag and Russian summary/description (the API docs are in Russian, so Russian keywords like "категории" work too). Any operation found here can be executed with kit_request; use get_operation_schema to inspect its parameters and body shape first.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOptional tag filter, e.g. "Товары" or "Вебхуки" (case-insensitive substring)
limitNoMaximum number of results to return (1-50, default 10)
queryYesSearch keywords (whitespace-separated, case-insensitive; every token must match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, and the description adds meaningful non-obvious context: the catalog size (179), the unusually broad match surface, and the fact that underlying docs are Russian so Cyrillic keywords work. It does not describe result shape or ordering, but with annotations covering the safety profile this is solid added value.

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?

Three sentences, each carrying distinct load: what is searched, why Russian keywords work, and what to do with the results. Front-loaded with the capability and sized well for the tool's simplicity.

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?

With only three params, all schema-documented, and no output schema, the description covers what matters: scope, search semantics, and the follow-up workflow. A minor gap is what a result entry contains (identifying field to feed into get_operation_schema), but the workflow link makes that inferable.

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 the baseline is 3, but the description goes further by explaining that queries match operationId, path, tag, and Russian text — telling the agent what kinds of keywords succeed, which the schema does not. It also gives a concrete example ('категории') that illustrates the non-Latin search behavior.

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?

States a specific verb and resource ('Search the full catalog of all 179 Yandex KIT API operations by keyword') and enumerates exactly which fields are matched (operationId, URL path, tag, Russian summary/description). This clearly distinguishes it from execution and schema-inspection siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: results here are executed via kit_request, and get_operation_schema should be used first to inspect parameters and body shape. That gives a clear discovery-to-execution workflow, though it gives no exclusion guidance (e.g., cases where a direct get_* tool would be preferable).

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