No user-submitted related servers found.
Scored across 10 tools
The set is organized around a deliberate search→detail pattern (search_objects→get_object, search_syntax→get_syntax, search_procedures→get_procedure), and each description explicitly states what the search step omits and why the detail step is mandatory. The three search_* tools target clearly separate domains (metadata objects, platform API, module code), and get_related (dependency graph) vs get_callers (call sites) are distinguished by scope. No two tools appear to do the same thing.
All ten tools follow a strict snake_case verb_noun convention (list_configurations, search_objects, get_object, compare_configurations, get_callers). Verb choice is semantically regular: search_* returns candidates, get_* returns detail, compare_* diffs, list_* enumerates.
Ten tools is well within the ideal range, and each one covers a distinct slice of the domain: configuration discovery, metadata exploration, platform syntax reference, and code navigation. Nothing looks redundant or bolted on.
The surface covers discovery, metadata structure, relations, cross-configuration diffing, platform API documentation, procedure search, procedure reading, and caller lookup — a coherent lifecycle for static analysis. Minor gaps remain: compare_configurations only diffs a single object's attribute names (no full-object or type/TabularSection diff), and there is no tool to validate or execute a constructed query, so agents must verify queries outside the server.