No user-submitted related servers found.
Scored across 38 tools
Several tools have unclear boundaries: core.compare_runs explicitly duplicates lens.compare_runs, and the tower.* family uses nearly identical descriptions for detect, investigate, preview, execute, verify, and related operations. The namespacing helps, but an agent could still misselect among overlapping compare, validation, and Tower action tools.
Tool names consistently use a namespace prefix plus lower_snake_case action, e.g. lens.analyze_workflow, chaos.run_experiment, and tower.incident. The main deviation is that some tower tools are nouns while others are verbs, but the overall convention remains readable and predictable.
With 38 tools, the surface is heavy even for a multi-subsystem server. The tower.* family alone is very large, and several tools appear to duplicate or overlap with others, making the count feel excessive rather than well-scoped.
The server covers a broad lifecycle across validation, analysis, release checks, incident investigation, chaos experiments, model routing, and session export. Some operations are intentionally delegated elsewhere, such as human approval via Tower HTTP/CLI, but the core workflows are mostly represented.
