No user-submitted related servers found.
Scored across 5 tools
Each tool maps to a distinct lifecycle action (start, status, help, call, stop) so an agent can generally tell them apart. The only mild overlap is cortex-status vs cortex-help, since both are informational endpoints, but their descriptions (session state vs tool schemas/safety context) do differentiate them.
All five tools use a uniform 'cortex-<verb>' naming pattern, making the set highly predictable. There is no mixing of casing or alternate verb styles.
Five tools is well-scoped for a runtime proxy/wrapper, covering exactly the lifecycle operations needed. No tool feels extraneous or missing from the count.
The surface covers the full session lifecycle (start/attach, status, help/discovery, call, stop) with discovery folded into start and help. A dedicated 'list allowed tools' operation might be a minor convenience gap, but the core loop is fully covered.
