MCP server for repository analysis and snapshot creation with deterministic tool handlers for read-only RepoGround access
Single tool 'snapshot_create' has a detailed input schema with 12 parameters, each with type and description. However, the tool description (89 chars) falls below the 10-1024 char baseline and lacks critical context: WHEN to use it, WHAT it returns, and WHY it matters. Parameter descriptions are present but generic (e.g., 'Snapshot profile name' without explaining available profiles or consequences). No output schema is documented, LLMs cannot plan downstream steps. The tool performs a WRITE operation (file creation) but the description does not explicitly state this, violating the command-tool pattern. No error handling guidance is provided.
Create a deterministic snapshot of a repository with configurable profiles, output modes, and file filtering
Tool description is too brief (89 chars) and lacks critical context. Does not explain WHEN to call it, WHAT it returns, or that it performs destructive file writes. Baseline: 10-1024 chars, 194 char average for A+ tools.
No output schema documented. LLMs cannot infer what fields are returned (e.g., snapshot_path, file_count, total_bytes, errors). This breaks tool chaining and forces agents to guess downstream parameter names.
Tool performs WRITE operations (creates files, may redact secrets) but description does not explicitly state this. Agents need to know which calls are safe to retry and which have irreversible consequences.
Parameter 'profile' references 'available profiles' but does not enumerate them or explain how to discover them. Code imports 'profile_names' but does not expose it as an enum constraint or discovery tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
No error handling guidance. Tool can timeout, exceed file size limits, or fail on invalid paths, but descriptions do not explain what to do next (retry, adjust parameters, call a discovery tool).