No user-submitted related servers found.
Scored across 9 tools
Each tool has a distinct role: preflight (pre-work obligations), find_overlaps (pre-authoring overlap check), decision_status (single-decision standing), cite_check (corpus-wide structural audit), search/explain/query for retrieval, and propose_decision for writes. The closest pair is preflight vs. find_overlaps, which both surface binding clauses, but their descriptions clearly separate 'before doing a task' from 'before writing a decision'. decision_status and cite_check also overlap mildly on staleness reporting, though at different granularities.
All names are lower snake_case, which is consistent. Most are verb_noun (search_decisions, explain_link, cite_check, find_overlaps, propose_decision, query_graph), but decision_status and graph_schema are noun_noun and 'preflight' is a bare noun with no verb, so the pattern is not fully uniform. Still readable and predictable enough.
Nine tools is well within the ideal range for a decision-graph server. Each tool maps to a recognizable workflow step (orient, search, inspect status, audit, draft, propose), and graph_schema is a small but justified companion to query_graph. No obvious redundancy or padding.
The surface covers the full decision lifecycle: search, standing checks, citation tracing, structural auditing, drafting, and committing via propose_decision. Minor gaps remain, such as no explicit get_decision for fetching a full decision body by ID (workable via search or query_graph) and no listing/timeline operation. Agents can work around these through the Cypher escape hatch, so no dead ends.