Scored across 27 tools
Every tool has a clearly defined role: omega_* tools handle context, storage, alignment, execution, and reporting, while veritas_* tools are specialized gates with discreet purposes and explicit cross-references (e.g., omega_rag_query vs omega_vault_search, omega_cortex_check vs omega_cortex_steer, veritas_evidence_gate vs veritas_compute_quality). The descriptions carefully disambiguate overlapping-sounding tools, so an agent can accurately select the right tool for a given task.
All names follow a consistent snake_case convention with a clear two-part prefix taxonomy: omega_* for brain/memory/governance operations and veritas_* for verification pipeline operations. Verbs and nouns are consistently separated and meaningful (e.g., ingest, search, check, steer, run_pipeline, resolve, transition), making the toolset predictable and scannable.
With 27 tools, the server exceeds the 25-tool threshold that marks an heavily oversized set. While each tool individually has a purpose, the sheer number places a significant cognitive burden on an agent and requires the agent to parse many near-similar gates and helpers; a more consolidated surface (e.g., merging that run_pipeline already wraps individual gates) might be more appropriate.
The toolset covers the full lifecycle of the domain: context loading, semantic storage/retrieval, alignment checking, audit sealing, session persistence, handoffs, and the total VERITAS 10-gate pipeline. Missing pieces are minor (e.g., no individual trace gate, no deletion/update operations for stored fragments), but the does not create blocking gaps for the can be worked around via the pipeline and report tools.
