Related Servers

There is significant overlap in several areas: hermes_skill_patch_proposal vs hermes_skill_patch_apply are distinct, but hermes_skill_eval_start vs hermes_eval_start vs hermes_eval_run vs hermes_api_runs_start all involve 'starting evals/runs' and could be confused. Similarly, hermes_status_overview and hermes_toolkit_info and hermes_detect_install and hermes_config_summary all aggregate overlapping read-only metadata. The docs_list/docs_read pair for API and Kanban API are parallel but distinguishable. The naming clearly delineates domains (skill vs config vs api vs kanban vs eval), but within domains several tools have similar purposes the agent may struggle to distinguish.

Tool names follow a consistent hermes_<domain>_<verb>_<noun> pattern throughout, using snake_case uniformly. The prefix structure is predictable (hermes_api_*, hermes_kanban_*, hermes_skill_*, hermes_eval_*), which helps agents navigate. Minor inconsistency: some use get vs read (hermes_api_models_list vs hermes_skill_read vs hermes_kanban_task_get), and _list vs _*_get conventions vary slightly, but the overall pattern is highly consistent and readable.

73 tools is far above the typical well-scoped range of 3-15, and this is a very heavy surface. While the server has broad breadth (install, config, skills, API wrappers, Kanban, evals, jobs, gateway), 73 tools will impose substantial cognitive load on agents when selecting, and many could be consolidated (e.g., the read-only status/toolkit/info/detect aggregation tools overlap heavily, and the 7 jobs_* tools and 8 kanban_task_* tools could be trimmed). At 73, even with broad scope, this is too many.

Within the domains covered, there's strong lifecycle coverage: jobs have create/get/update/list/delete/pause/resume/run; Kanban tasks have create/update/get/comments/bulk/run_decompose; API responses have create/get/delete; runs have start/get/stop/events/approval. The addition of an agent_ask_fallback plus docs tools shows thoughtful coverage. Minor gaps exist—there's no explicit Kanban task delete, no board create/delete tool despite board_get/list, and no Kanban comments list/delete—but the core workflows are well covered. The eval surface has run/start/status/cancel which is complete.