Related Servers

Every tool has a clear, distinct purpose. Dispatch pair (explicit/auto) is well-differentiated by naming and descriptions. Other tools like doctor, inbox, send, status, tasks, etc. are uniquely scoped with no overlap.

All tools follow the 'trinity_' prefix with a consistent verb_noun pattern (e.g., trinity_dispatch, trinity_skill_load, trinity_worker_daemon). No mixed conventions or ambiguous names.

With 12 tools, the set is well-scoped for a multi-agent orchestration server. It covers dispatching, messaging, skills, health, worker management without being excessive or thin.

The tool surface covers the core lifecycle: task creation, dispatching, orchestration, messaging, skill management, and monitoring. Minor gaps exist (e.g., no explicit task cancellation or message deletion), but these are not critical for the domain.