Scored across 22 tools
Several session- and command-related tools overlap in concept, but descriptions explicitly cross-reference each other and guide selection (e.g., list_agent_sessions vs find_agent_session vs search_commands). A few boundaries remain subtle, such as get_agent_session vs replay_agent_session and list_sessions vs session_history, but overall an agent can tell the tools apart.
All names use snake_case, which is consistent, but the naming pattern is mixed: many use verb_noun (list_agent_sessions, get_stats, search_skills) while others are noun phrases or interrogatives (project_context, recent_commands, what_changed). The set is still readable, but the lack of a single predictable verb_noun pattern is a notable deviation.
At 22 tools, the surface is heavy for a single MCP server, though the domain—command history, agent sessions, skills, snippets, and risk assessment—is broad enough to justify many of them. The count falls into the borderline range where the set risks being overwhelming despite each tool having a plausible role.
Core workflows for command search, session discovery, agent-session replay, failure analysis, statistics, and risk assessment are well covered, with no obvious dead ends for read/analysis use. The main gap is the absence of create/update/delete operations for skills and snippets, though those may intentionally live in CLI or file-based workflows.
