No user-submitted related servers found.
Scored across 8 tools
The four rule-readers (get_rule, get_rule_as_of, get_rule_history, resolve_version) operate on the same shapes and could be confused at a glance, but descriptions and worked examples make the split (current / date-scoped / all versions / pinned id) explicit. compare_jurisdictions overlaps with get_rule but is clearly framed as the batch form, and the two registry readers (list_jurisdictions, list_rule_types) are cleanly separated from the change feed.
Every name is verb-first snake_case (list_*, get_*, compare_*, resolve_*), with the get_rule family following a predictable base + modifier pattern. No mixed camelCase or vague single-word verbs anywhere.
Eight tools is tight and well scoped for a read-only legal-rules API: two discovery tools, four lookup modes that map to genuinely different temporal semantics, one comparison, one change feed. Nothing appears redundant or padding the surface.
The read lifecycle is well covered: discovery, point-in-time lookup, full version history, immutable version pinning for audit, cross-jurisdiction comparison and a change feed with cursors. Minor gaps: no full-text/keyword search over rule content or citations, and no way to enumerate which rule types apply to a given jurisdiction in one call (callers must loop get_rule per type).