CLI-first MCP server: routes AI requests through gemini and codex CLIs with OpenRouter fallback
Critical gaps across all 18 tools. No visible input schemas in provided source code, cannot verify parameter types, constraints, or descriptions. Tool descriptions are present but generic (10-50 chars), lacking WHAT/WHEN/WHY context required by LLMs. No documented output schemas. Tool names lack action verbs (e.g., 'chat', 'clink', 'thinkdeep' are vague; should be 'start_chat', 'bridge_to_cli', 'analyze_deeply'). No evidence of error handling, recovery guidance, or parameter validation. Base infrastructure (BaseTool) exists but actual tool implementations not visible in source excerpt.
Code analysis tool
Challenge and critique analysis tool
Interactive development chat and brainstorming
Bridge requests to configured AI CLIs
Comprehensive step-by-step code review workflow with expert analysis
Step-by-step consensus workflow with multi-model analysis
Root cause analysis and debugging assistance
No input schemas visible for any of 18 tools. Cannot verify parameter types, constraints, enums, or descriptions.
Tool names lack action verbs. 'chat', 'clink', 'thinkdeep', 'analyze', 'lookup' are vague. LLMs infer intent from names, should be 'start_chat', 'bridge_to_cli', 'perform_deep_analysis', 'analyze_code', 'search_or_lookup'. Baseline: 90% of A+ tools start with action verb.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 26 | 2026-07-28+ | v2 |
Step-by-step documentation generation
List available AI models
Lookup and search tool
Interactive sequential planner using workflow architecture
Step-by-step pre-commit validation workflow
Code refactoring tool
Comprehensive security audit with OWASP Top 10 and compliance coverage
Test generation tool
Step-by-step deep thinking workflow with expert analysis
Code tracing and execution flow analysis tool
Display server version information
Descriptions are generic and under 50 chars for most tools (e.g., 'Code analysis tool', 'Lookup and search tool'). Need WHAT/WHEN/WHY context for LLM selection.
No documented output schemas. LLMs cannot plan downstream calls or extract required fields.
No error handling or recovery guidance visible.