An MCP server providing file system operations, text search, JSON/YAML selection, file hashing, and git log querying with caching and metrics
Toolpilot provides 9 read-only file/git tools with complete JSON schemas and reasonable descriptions. All tools have input schemas with typed parameters and descriptions. However, descriptions are terse (avg ~60 chars, well below the 194-char baseline), lack context on WHEN to use each tool, and omit dependency hints. Parameter descriptions are minimal. Output schemas are not documented. Error handling is generic ('error' field only, no recovery guidance). No tool annotations (readOnlyHint present implicitly via Risk field, but not in schema). Naming is clear and verb-based (fs_glob, text_search, read_file), following conventions well.
Compute cryptographic hash of file contents
Find files matching glob patterns in a base directory
Generate a tree view of directory structure
Query git commit history for a repository
Extract values from JSON files using JSONPath-like selectors
Read the contents of a file with optional byte limit
Get server metrics including cache statistics and request counts
Descriptions are terse (avg ~60 chars vs 194-char baseline). Missing WHEN to use each tool and dependency hints. E.g., 'Find files matching glob patterns' lacks context on when to call fs_glob vs fs_tree.
Output schemas not documented. LLMs cannot infer what fields each tool returns, forcing them to guess downstream field names for chaining calls.
Error handling is generic ('error' field only). No recovery guidance. E.g., if a file is not found, the error should suggest 'Try fs_glob() to locate the file first.'
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2025-06-18+ | v2 |
Search for text patterns in files using regex
Extract values from YAML or TOML files using dot-notation selectors
No tool annotations in schema. Risk field in metadata is not machine-readable. Should add readOnlyHint: true to all tool schemas per current spec.
Parameter descriptions are minimal. E.g., 'Glob patterns to match files against' lacks format guidance. Should specify: 'Glob patterns (e.g., **/*.rs, src/*.json). Supports *, ?, [abc] syntax.'