MCP server for file operations supporting preload, read, read_multiple, and close operations on memory-mapped files
Single tool 'fileop' has a detailed input schema with proper JSON Schema structure (types, enums, descriptions for most parameters). However, the tool description is generic and lacks actionable context for LLM selection. The schema is visible in the rubric input but the actual tool registration code in FileOpController.cpp is truncated mid-definition, preventing full verification of output schema documentation. The tool performs multiple distinct operations (preload, read, read_multiple, close) under one name, violating single-responsibility principle. No error handling guidance, no output schema documented, no recovery hints.
File operations tool supporting preload, read, read_multiple, and close operations on memory-mapped files
Tool name 'fileop' is generic and does not start with a clear action verb. It bundles four distinct operations (preload, read, read_multiple, close) into one tool, violating single-responsibility. Should be split into separate tools: preload_file, read_file, read_multiple_files, close_file.
Tool description 'File operations tool supporting preload, read, read_multiple, and close operations on memory-mapped files' is 119 characters but lacks WHEN to use it, WHAT it returns, and WHY it exists. No guidance on prerequisites (e.g., must preload before read). LLMs cannot determine when to select this tool over alternatives.
Output schema is not documented in visible source. FileOpController.cpp is truncated at the tool definition. Cannot verify what fields are returned for each operation (preload, read, read_multiple, close) or whether responses include IDs for chaining.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
No error handling guidance. Errors like 'Invalid handler', 'Read out of bounds', 'Invalid format' are returned but do not tell the LLM what to do next (retry? ask user? call preload first?). No recovery hints.
Parameter 'operation' is an enum but lacks a description explaining what each operation does. Parameter 'handler' is described as 'Handler ID from preload' but does not explain the format or how to obtain it if preload fails. Parameter 'segments' is complex (nested array of objects) but lacks examples or clear guidance on structure.