MCP for Russian ad marking: erid format check; ORD cabinet lookup on the client key. Advisory only.
Server has 6 tools with basic schemas and descriptions, but significant quality gaps. Tool names lack action verbs (verify_erid, lookup_erid, audit_ad_page, check_compliance_38fz, explain_topic, audit_batch). Descriptions are present but many are in Russian and several tools explicitly state they are NOT implemented ('ещё не подключены'). Input schemas exist but are minimal, most parameters lack detailed constraints, ranges, or format guidance. Three tools (audit_ad_page, check_compliance_38fz, audit_batch) are stubs that return honest refusals rather than functional implementations. No output schemas documented. Error handling is present in code but not reflected in tool definitions. No tool annotations (readOnlyHint, destructiveHint, idempotentHint).
Разбор рекламной страницы ещё не подключён. Честный отказ, не «маркировки нет».
Пакетная проверка рекламных страниц ещё не подключена.
Чек-лист 38-ФЗ по живой странице ещё не подключён. Честный отказ.
Краткая справка по маркировке. Не реестр и не юридическое заключение.
Поиск креатива в кабинете ОРД клиента. Сейчас по открытому описанию — ОРД VK. Не общий ЕРИР.
Проверка формата токена erid (длина и символы). В ЕРИР не ходит. Бесплатно, без ключа.
Tool names lack action verbs. 'verify_erid', 'lookup_erid', 'audit_ad_page' do not follow verb_noun pattern. Should be 'check_erid_format', 'search_erid_in_cabinet', 'audit_ad_page_marking'.
Three tools (audit_ad_page, check_compliance_38fz, audit_batch) are not implemented, they return honest refusals. These should either be removed from the tool list or marked as unavailable. Exposing non-functional tools wastes LLM reasoning cycles.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract fields without knowing the response structure. All tools need documented return types.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | <=2025-11-25 | v2 |
Input parameter descriptions lack format guidance and constraints. 'erid' parameter has minLength=1 but no pattern, length limit, or example format. 'topic' parameter in explain_topic has no enum of valid values (erid, ord, erir, responsibility, deadlines, fines).
Descriptions are in Russian, making them inaccessible to non-Russian-speaking LLMs and developers. Tool descriptions should be in English for international use.