No user-submitted related servers found.
Scored across 12 tools
Each tool has a discernible scope: lookups (system vars, KSS messages), syntax reference, snippet lint, workspace diagnostics, safety audit, repair, and telemetry are textually distinct. The only mild overlap is in the static-analysis family (krl_lint_snippet vs krl_workspace_diagnostics vs krl_deep_safety_audit), but descriptions clearly separate offline-snippet, project-wide, and motion/payload-safety concerns.
All 12 tools share the krl_ prefix and snake_case formatting with descriptive multi-word suffixes, giving a predictable namespace. There is a minor style split between verb-first names (krl_read_file, krl_lint_snippet, krl_lookup_*) and noun-phrase names (krl_syntax_reference, krl_control_flow, krl_live_telemetry), but readability and consistency remain high.
Twelve tools is a well-scoped set for a KRL development/assistant server, with each tool covering a distinct capability (connection, telemetry, references, analysis, repair, workspace access). No filler or redundant tools are apparent.
The surface covers the core read/analyze/repair lifecycle plus live controller telemetry and reference lookups, which is broad for the domain. Gaps remain: there is no write/save-file or create-program tool (krl_safe_auto_repair only returns repaired text), and no cross-workspace symbol search, but agents can work around these.