A file search MCP server that finds files in a directory based on name fragments
This MCP server has a single tool, find_files, which suffers from critical definition quality gaps. The tool name lacks a clear action verb and the description is in Russian, making it inaccessible to most LLM contexts. While the input schema is present with proper types and descriptions (also in Russian), the descriptions are minimal and lack the strategic guidance LLMs need for tool selection. The implementation shows no output schema documentation, no error handling guidance, and no input validation patterns. The tool performs a basic file search across a directory tree but is not optimized for agent interaction patterns.
Ищет файлы в указанной директории, имя которых содержит фрагмент, переданный в аргументе fragment_name.
Tool name does not follow verb_noun convention; 'find_files' is acceptable but lacks context about what 'find' means (search by name, regex, content, metadata?). Name is ambiguous about search scope.
All descriptions (tool and parameters) are in Russian, making the server inaccessible to English-speaking LLM contexts and violating the standard MCP convention of English-only metadata.
Tool description is 135 characters but lacks strategic context: WHEN should the LLM call this instead of a shell command? WHAT does it return? Is output paginated? No guidance for agent selection.
No documented output schema. LLMs cannot plan downstream calls without knowing the response structure. The code returns a list of dicts with 'name', 'path', 'size', 'created', but this is invisible in the tool definition.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 38 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 38 | - | v1 |
No pagination support. A recursive directory walk over /home could return thousands of files, exhausting context windows. No limit parameter, no offset/page parameters, no total count in response.
No error handling guidance. What happens if fragment_path does not exist? (Code checks and exits with error, but no recoverable error message.) What if search returns 0 results? No distinction between 'nothing found' and 'permission denied'.
Parameter 'fragment_path' could accept a relative path that traverses parent directories (../../etc/passwd) or an invalid path. No validation guidance in description; no constraint on format (absolute vs relative vs glob).
Parameter 'fragment_name' accepts any string and is matched with 'in' operator (substring match). Description does not clarify: is matching case-sensitive? Does it support regex or globs? What characters are valid?
No idempotence guarantee. If an LLM retries the same find_files call, it will return the same results IF filesystem state is unchanged. But the implementation does not document this, and file modification times could change between calls, leading to confusion.