No user-submitted related servers found.
Scored across 18 tools
Several tools occupy overlapping impact/navigation territory: strata_impact, strata_validation_scope, and strata_navigate all return affected views/explores/fields, while strata_find_field and strata_query_field have similar search/query semantics. strata_list_orphans and strata_dead_code_register also blur together. Without more detailed descriptions, an agent could easily select the wrong tool.
All tools share the strata_ prefix and use snake_case, which provides a consistent namespace. However, the verb_noun pattern is not maintained: list_orphans and find_field sit alongside bare noun phrases like ir_status, pdt_costs, schema_drift, and conductor_status. The singular strata_skill also breaks the list/detail convention established by strata_list_skills.
18 tools is above the typical 3-15 well-scoped range and mixes core data-model analysis tools with meta utilities like skills, conductor status, and chart templates. It is not extreme, but the set feels heavier and broader than necessary for a focused server.
For a read-only data-model navigation and impact-analysis server, the surface covers discovery, dependency exploration, impact assessment, orphan/dead-code detection, schema drift, usage, costs, and even rendering charts. Minor gaps exist, such as no explicit per-explore detail tool and no apply flow after validation_scope, but agents can generally work around these.