Loading ToolBench
A document translation service that translates text to target languages
This MCP server has critical definition quality issues. The single tool 'translate_doc' lacks proper MCP server structure, has a minimal description (33 chars), and no visible output schema documentation. The source shows only a Python client class, not an MCP server implementation. There is no evidence of MCP protocol integration, tool registration, or proper schema definitions. The code appears to be a standalone Python utility, not an MCP-compliant server.
Translates document text to a target language
Tool description is critically short (33 characters). Missing WHEN to use, dependencies, and expected behavior.
No output schema documented. LLMs cannot plan downstream tool calls or extract return data without knowing expected fields. The code returns {'translated_text': ...} but this is inferred, not formally documented in the tool definition.
Parameter descriptions are present but minimal (e.g., 'The text to be translated' is only 28 chars; baseline is 72 chars). Missing detail on expected length, character restrictions, language encoding, and pre-processing needs.
Target language parameter lacks enumeration or constraint. The description says 'language code for translation' but does not state valid values (e.g., ISO 639-1 codes like 'ES', 'FR', 'DE'). This invites LLM hallucination of invalid codes.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | 2026-07-28+ | v2 |
No error handling documented. The tool offers no recovery guidance if translation fails (e.g., unsupported language, input too large, API timeout). LLMs receive no signal for retryability or fallback.
No evidence of MCP server implementation. Source code shows only a Python client class (DocumentTranslatorClient) and example usage. No MCP protocol integration, no tool registration mechanism, no transport layer (STDIO, HTTP, etc.). This appears to be a standalone utility, not an MCP server.
Input schema has parameter types (string) but no format, length, or regex constraints. The 'text' parameter accepts any string with no limits; the tool should document max length and encoding expectations.