fs-mcp-server provides a filesystem toolkit with 9 tools, all properly registered with schemas and descriptions. Naming follows verb_noun pattern consistently (list, read, write, mkdir, delete, copy, move, info, search). All tools have descriptions between 18 - 45 characters, meeting the 10 - 1024 baseline. Input schemas use JSON Schema with typed parameters and descriptions. However, output schemas are not documented in the provided source, no response structure specifications visible. Parameter descriptions are present and describe purpose and format constraints, but some lack explicit value ranges or format patterns. Error handling exists (via Rust Result types and anyhow crate) but recovery guidance is not visible in descriptions. Security is well-managed via AllowedPaths validation and no exposed secrets in parameters.
Copy files or directories
Delete files or directories
Edit file contents with multiple operations
Get detailed information about a file or directory
List files in a directory
List all allowed directories configured for this server
Create directories
Move or rename files or directories
Read file contents
Output schemas not documented. No visible response type definitions for any of the 9 tools. LLMs cannot plan downstream calls or extract structured data without knowing what fields are returned.
Destructive operations (delete, write in overwrite mode) lack confirmation or dry-run patterns. No visible confirmation_required field or dry_run parameter to prevent accidental data loss.
Parameter constraints incomplete. 'encoding' parameter in read/write lacks enum values (utf8, ascii, latin1). 'mode' in write has enum but no description of default behavior. Numeric limits (e.g., max_results in search defaults to 100) are present but not enforced as min/max in schema.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 7 | <=2025-11-25 | v2 |
| 2026-03-09 | D | 57 | - | v1 |
Search file contents for matching patterns
Write content to a file
No recovery guidance in error descriptions. If a delete fails or a path doesn't exist, LLM cannot infer next steps from error messages (no visible error message templates or suggestions in tool descriptions).
No pagination or result limits documented for list and search. 'list' with recursive=true on large directory trees could return unbounded results. 'search' has max_results default=100 but no warning if response truncates.
Tool descriptions do not explicitly state which operations modify state. 'write' and 'delete' descriptions lack clarity on irreversibility and retry semantics required by pattern:command-tool.