Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Execute any KIT API operation

kit_request

Execute any Yandex KIT API operation by operationId, including those without a dedicated tool. Validates request bodies against OpenAPI schemas before making real store calls.

Instructions

Escape hatch that executes ANY of the 169 Yandex KIT API operations by operationId, including operations without a dedicated tool. WARNING: this performs REAL calls against the live store — write operations (create/update/delete/archive) take effect immediately and there is no sandbox. Workflow: search_operations -> get_operation_schema -> kit_request. The request body is validated against the OpenAPI schema before sending (set validate=false to skip).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoJSON request body; get the exact shape from get_operation_schema("<OperationId>")
queryNoQuery-string parameters (e.g. page, per_page for paginated lists)
validateNoValidate body against the OpenAPI schema before sending (default true)
path_paramsNoValues for {placeholders} in the path, e.g. {"id": "123"}
operation_idYesOperation id in PascalCase, e.g. "GetProducts" (find it via search_operations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations, so the description carries the full burden and does so well: discloses that calls hit the live store, write operations take effect immediately, there is no sandbox, and that the body is validated against the OpenAPI schema (with validate=false to skip). These are critical behavioral traits beyond what the schema provides.

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?

Front-loads the core purpose, then the critical warning, then the workflow. Every sentence earns its place with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex escape-hatch tool with no output schema, the description covers what the tool does, how to use it, and the critical safety caveats. An agent has everything needed to invoke it correctly and safely.

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?

Schema description coverage is 100%, so the schema already documents each parameter with examples and types. The description adds little parameter-level detail beyond the workflow pointer, which is appropriate given the rich schema. Baseline 3.

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+resource ('executes ANY of the 169 Yandex KIT API operations by operationId') and explicitly distinguishes itself from the many dedicated sibling tools by being the escape hatch for operations without a dedicated tool. Clear 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 Guidelines5/5

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

Provides an explicit workflow: 'search_operations -> get_operation_schema -> kit_request.' Names the alternatives (dedicated tools) and the condition for using this one (operations without a dedicated tool).

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