Multi-service MCP server providing read-only access to Yandex Direct API, Yandex Search API, and Yandex Wordstat API
Server has 7 tools with mixed quality. Tool naming is inconsistent: some use verb-noun (get-regions-tree, get-region-children, top-requests, dynamics), others are domain-specific (yd_api, ai_search_with_yazeka, web_search). Descriptions vary widely in quality and length. Most critical: yd_api lacks parameter descriptions for 'params' (JSON object), ai_search_with_yazeka and web_search have warnings in Russian that don't guide LLM behavior, and several tools lack output schema documentation. Parameters have types but many lack actionable constraints or format guidance. No evidence of error handling patterns or recovery guidance.
Платный порождающий поиск. Не вызывай его без явно выбранного платного режима.
Returns search volume dynamics (trend) for a keyword over time. Note: all search operators work at daily granularity; weekly/monthly granularity supports only the "+" operator.
Returns the children of a specific region. Use this to drill down into a region from get-regions-tree.
Returns the top 3 levels of the Wordstat regions tree (countries, federal districts, major regions). Use get-region-children to drill down into specific regions.
Returns popular search queries containing the specified keyword for the last 30 days, plus similar/associated queries. The phrase supports Wordstat search operators.
yd_api 'params' parameter lacks description and format guidance. Accepts arbitrary JSON but no documentation of valid structure, required fields, or examples. LLM cannot determine what to pass.
ai_search_with_yazeka and web_search descriptions contain Russian-language warnings ('Платный...') that do not guide LLM behavior. Warnings should be in English and structured as actionable constraints or permission gates, not natural language caveats.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. Responses are opaque.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2025-06-18+ | v2 |
Платный веб-поиск. Не вызывай его без явно выбранного платного режима.
Выполнить разрешённый get без передачи токена в аргументах.
No error handling or recovery guidance. Tools do not document what errors are retryable, what user input is needed, or how to self-correct. LLM has no path forward on failure.
Inconsistent tool naming convention. Python tools use snake_case (yd_api, ai_search_with_yazeka), Node tools use kebab-case (get-regions-tree, top-requests). LLM must learn two naming styles.