No user-submitted related servers found.
Scored across 11 tools
Each tool targets a distinct capability: language reference, stdlib lookup, project overview, single-definition detail, effect graph, static checking, formatting, execution, testing, change diff, and embedding chunks. Overlaps (e.g., project_map vs chunks) are clearly separated by their descriptions and output formats, so an agent can reliably select the right tool.
All names use snake_case, but the set mixes noun-based names (cheat_sheet, project_map, definition, effects, chunks) with verb-based names (check, format, run, diff) and one verb_noun (run_tests). There is no single predictable pattern like verb_noun throughout, though the names remain readable and descriptive.
11 tools is well-scoped for a language toolchain, covering documentation, inspection, checking, formatting, execution, testing, diffing, and embedding without obvious redundancy. Each tool earns its place and the count sits comfortably in the ideal 3–15 range.
The surface covers the core lifecycle: reference, stdlib lookup, project map, definition detail, effect graph, check, format, run, test, diff, and chunks. Minor gaps remain, such as no project-wide search by name (one must scan project_map) and no direct file editing or scaffolding, but agents can work around these.