Loading ToolBench

Reading the current corpus…

diadoc-mcp-ru MCP server · F · ToolBench

diadoc-mcp-ru

API Диадока для ИИ-ассистентов: входящие и исходящие документы, статусы документооборота, контрагенты и приглашения к ЭДО, подписание, МЧД, печатные формы

2026-07-28+STDIO1 tools

38/100

Definition Quality30

Protocol Readiness50

Supportability42

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Only 1 tool visible in source (diadoc_get_my_user). Tool has a basic description (28 chars, below 20-char floor) and no visible input schema in the provided code. The server delegates tool registration to schema-mcp-core library functions (register_generic_tools, register_cabinet_tools), making actual tool definitions and schemas not directly verifiable from this source. Since the one visible tool has inadequate description and no schema visible, score is lower.

Tools (1)

diadoc_get_my_userread onlyauthsource verified30/100

Get authenticated user information (FullName, Login)

Issues (5)

CRITICALtool ↗

Tool definitions delegated to external library (schema-mcp-core); actual schemas, parameter descriptions, and output structures not visible in source code. Cannot verify compliance with JSON Schema, parameter typing, or output documentation.

diadoc_get_my_user

HIGHtool-description ↗

diadoc_get_my_user description is 28 characters ('Get authenticated user information (FullName, Login)'), below the 20-char floor for scoring. Lacks WHEN to use, prerequisites, or state-change implications. Does not meet pattern:tool-description baseline of 34 - 392 chars.

diadoc_get_my_user

CRITICALconstrained-input ↗

No input schema visible for diadoc_get_my_user. Cannot verify parameter types, descriptions, enums, or constraints.

diadoc_get_my_user

HIGHresponse-shaper ↗

No output schema documented. LLMs cannot plan downstream calls or extract fields without knowing the response structure (e.g., does it return {FullName, Login} as strings, or nested objects?).

Recommendations

Expand diadoc_get_my_user description to 50 - 150 chars: 'Retrieve the authenticated user's full name and login. Call this first to verify credentials and identify the current user before making other API calls.'
Document the output schema explicitly: {FullName: string, Login: string}. Include in tool description or as a separate schema reference.
If the library (schema-mcp-core) generates tools dynamically from endpoints.yaml, verify that endpoints.yaml includes parameter descriptions, type definitions, and output schemas for all 114 methods. Audit a sample of 5 - 10 endpoints to confirm schema completeness.
Add error handling guidance: 'If authentication fails, verify DIADOC_CLIENT_ID and DIADOC_TOKEN are set correctly. Contact diadoc-api@skbkontur.ru for a new client ID.'
Document which tools are read-only vs. destructive. The ingest script marks some as 'destructive' (Delete*, Recycle*, Break*), expose this in tool annotations (readOnlyHint, destructiveHint) so agents know which calls are safe to retry.

Score history

Overall score trend

First recorded score · v2 rubric

38/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	38	2026-07-28+	v2