MCP server for orchestrating multi-file semantic refactoring with atomic diff composition, AST syntax verification, and git-ready commit generation
This server has severe definition quality issues. Tool 1 (execute_skill_action) has no visible input schema or parameter documentation. Tool 2 (orchestrate_multi_file_semantic_refactor) has a basic schema with only 2 parameters, both strings with minimal descriptions. Neither tool has descriptions that explain WHEN to use them, WHAT they return, or error recovery paths. The descriptions are under 100 chars and lack actionable context. No output schemas are documented. No error handling guidance. The server appears to be a mock/stub implementation rather than a production-ready MCP server.
Execute a skill action for multi-file semantic refactoring orchestration
Orchestrate multi-file semantic refactoring with atomic diff composition, AST syntax verification, and speculative diff preview
Tool 1 (execute_skill_action) has NO visible input schema and NO parameter documentation.
Tool 2 naming is problematic: 'orchestrate_multi_file_semantic_refactor' is 40+ chars, vague, and contains 'and' (atomic diff composition AND AST verification AND speculative preview). Should split into separate tools: verify_ast_syntax, preview_diff, apply_atomic_diffs.
No output schemas documented for either tool. Tool 2 returns a dict with 6 fields (composer_task_id, target_path, files_analyzed_count, etc.) but this structure is not declared in the tool definition. LLMs cannot plan downstream calls without knowing return types.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 22 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If refactoring fails, the LLM has no guidance on what to do next. No categorization of errors as retryable vs fatal.