No user-submitted related servers found.
Scored across 23 tools
Each tool has a clearly distinct role: reads (search, resolve, traverse, aggregate, history), writes (prepare/commit), batch operations, and import. Although legacy direct-write tools overlap with the prepare/commit workflow, they are explicitly marked as legacy and direct agents to the new flow, eliminating ambiguity.
Most tools follow a consistent verb_noun pattern (create_record, search_records, get_record_history), but a few break the pattern with noun-first names like batch_read and batch_resolve_records, and aggregate stands alone as a bare verb. Minor deviation, still readable.
23 tools is on the higher side, but the scope is broad: collections, records, links, two-phase commits, batch operations, import, search, and audit. Six legacy tools duplicate the prepare/commit surface, adding weight, but the core tool set is still well-scoped for the domain.
The surface covers the full lifecycle: collection discovery and creation, record create/read/update/archive, linking/unlinking, resolution, search, aggregation, graph traversal, history, and atomic batch/import operations. The only apparent absence is permanent deletion, which seems intentional in an audit-focused system.