Related Servers

The execution and approval tools are mostly distinct, but the inspection tools overlap: hermes_plan and hermes_capabilities both imply inspecting capabilities, hermes_status is a subset of hermes_capabilities, and hermes_presets is explicitly listed inside capabilities. Descriptions help clarify, but an agent could still hesitate when choosing between run, submit, and prepare/approve for executing work.

All tools share a consistent hermes_ prefix, and most actions use clear imperative verbs like run, plan, submit, cancel, prepare, approve, and reject. However, some tools are noun-style names (hermes_capabilities, hermes_presets, hermes_status, hermes_result) rather than verb_noun names, and hermes_job_status breaks the pattern by combining a noun with a status word. Overall readable and predictable, but not perfectly uniform.

Twelve tools is a reasonable scope for a bridge that covers runtime inspection, capability discovery, synchronous execution, asynchronous job management, and a human-approval flow. Each tool serves a distinct part of the interaction lifecycle, and none feel redundant or unnecessary.

The tool surface covers the core lifecycle well: inspect capabilities, run or plan work, submit async jobs, check status, retrieve results, cancel jobs, and handle approval/rejection. Minor gaps exist such as no way to list all running or pending jobs/approvals, but agents can still accomplish the main workflows without hitting dead ends.