MCP Server for Constraint Satisfaction Problem solving using AC-3 arc consistency and backtracking with Minimum Remaining Values heuristic
Single tool with adequate schema but critical gaps in description quality and parameter documentation. Tool name lacks action verb. Description is 156 chars (within range) but lacks WHEN/WHY guidance. Input schema present with types and descriptions, but parameters lack actionable constraints. No output schema documented. No error handling guidance. Fails multiple baseline checks for A/B/C tier tools.
Solve a map coloring constraint satisfaction problem using AC-3 arc consistency and backtracking search
Tool name 'solve_map_color' lacks action verb. Should be 'solve_csp_map_coloring' or 'find_map_coloring_solution' to signal intent clearly to LLMs.
No output schema documented. Tool returns {'solution': sol} but LLMs cannot infer structure of 'sol' (dict? list? null on failure?). Must document return type explicitly.
Parameter descriptions lack actionable constraints. 'domains' description says 'Dictionary mapping...' but does not specify: required? empty dict allowed? value type (must be list of strings)? Format of keys?
No error handling guidance. Tool can fail (unsatisfiable CSP, empty domain after AC-3, invalid constraint). No recovery hints for LLM (e.g., 'Try relaxing constraints' or 'Increase domain size').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Tool description does not explain WHEN to use it vs alternatives, prerequisites, or what 'solution' contains. Baseline for A+ tools: 50-200 chars with WHAT/WHEN/WHY. Current: 156 chars but missing WHEN/WHY.