Scored across 36 tools
The tools span distinct subsystems (mesh, ChainLock, AKM memory, FragGate, raw sessions), and descriptions explicitly cross-reference alternatives. However, multiple exec doors (fraggate_call, runtime_run, runtime_session_exec) and parallel recall/append paths (chainlock_* vs memory_*) create real misselection risk despite the verbose warnings.
Most tools follow a snake_case prefix_action pattern (mesh_join, chainlock_append, runtime_session_open). Deviations exist: 'Softwares' is capitalized and noun-only, and runtime_* mixes verbs and nouns (runtime_run, runtime_bundle, runtime_manifest). Mixed but still largely readable.
36 tools is well above the 3–15 sweet spot and exceeds the 25+ threshold for 'too many'. While the server covers many subsystems, the surface is sprawling and includes redundant advanced/internal doors.
Core lifecycles are covered: session open→policy→exec→receipt→close, mesh join/heartbeat/leave/status, ChainLock append/tip/recall/verify/seal, memory observe/resolve/calibrate/recall/get. Minor gaps exist (e.g., mesh_disable is a refuse rather than a real off switch, no delete paths by design), but agents can work around them.