MCP server that finds and processes literal Unicode escape sequences in files, either decoding them to actual characters or stripping them entirely
Single tool 'unicode_remove' has a clear, specific name starting with a verb and a detailed description (180 chars). Input schema is fully defined with 4 parameters, all typed and described. However, output schema is not documented, the tool returns a Result struct with fields like 'replacements', 'bytes_in', 'bytes_out', but the agent has no visibility into this structure. Error handling is minimal: the tool returns generic -32603 'Execution failed' messages without guidance on recovery or categorization. No dry-run confirmation pattern despite the tool being destructive (modifies files). Parameter descriptions lack format constraints (e.g., what constitutes a valid 'mode' value beyond the description text).
Find literal Unicode escape sequences (\uXXXX, \UXXXXXXXX, \u{XXXX}) in a file and either decode them to actual characters or strip them. Operates only on a file path so escape sequences are not lost to JSON-decoding before reaching disk.
Output schema not documented. Tool returns a Result struct with fields (replacements, bytes_in, bytes_out, backup, status) but agents have no visibility into the response structure. LLMs cannot plan downstream actions or extract relevant data.
Error handling lacks recovery guidance. Generic -32603 'Execution failed' errors do not tell the agent what went wrong or what to do next. No categorization of errors as retryable vs. fatal.
Destructive tool lacks confirmation pattern. Tool modifies files on disk (with optional backup). No dry-run enforcement or explicit confirmation step before irreversible changes. Agents can accidentally corrupt files.
Parameter 'mode' lacks enum constraint. Description states 'decode = ... delete = ...' but no formal enum in schema. LLMs may pass invalid values like 'strip' or 'remove' instead of the two valid options.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 68 | 2026-07-28+ | v2 |
No input validation or actionable error messages. If 'file' parameter is invalid (non-existent, unreadable, or not absolute path), the tool returns a generic error. Should validate early and return 'File not found: /path/to/file' or 'Path must be absolute'.