No user-submitted related servers found.
Scored across 5 tools
The five tools map to distinct stages: load/declarations (validate), authoring diagnostics (check), behavioral assertions (test), decision explanation (explain), and forward impact tracing (dependents). The only genuine near-overlap is validate vs check, since both load a single-file program, but the descriptions explicitly contrast them (declaration summary vs diagnostics) and cross-reference alternatives in each entry. Explain and dependents both replay events, but their output focus (all decisions vs one subject's reach) is clearly separated.
All tools share the caveat_ prefix followed by a short verb-ish token (validate, check, test, explain, dependents), yielding a predictable, scannable set. The lone deviation is caveat_dependents, which is a noun rather than a verb, but it still reads naturally and consistently with the prefix scheme.
Five tools is well-scoped for a language authoring/analysis server, and each corresponds to a non-redundant stage of the workflow (load, diagnose, assert, explain, trace). No tool feels like padding or a mere variant of another.
The surface covers the full authoring lifecycle: load/validate, static diagnostics, behavioral testing with scenarios, and post-hoc explanation plus dependency tracing over event replays. Minor gaps exist — there is no tool to persist or manage multiple source files or scenario documents, and no standalone event-dispatch/step-through tooling — but the documented inline-source workflows are end-to-end usable.