hermes-action-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hermes_runC | Use Hermes-owned skills, connected services, browser workflows, messaging, schedules, or external automation through bridge policy. Do not use for ordinary local code edits. |
| hermes_planA | Ask Hermes to inspect its configured capabilities in plan mode. Hermes may access open-world tools, so review the response before taking or approving an external action. |
| hermes_capabilitiesA | Inspect bridge status, configured presets, skills, toolsets, providers, models, and policy before deciding whether Hermes owns the requested capability. |
| hermes_presetsA | List configured bridge presets and their declarative Hermes skills and toolsets. |
| hermes_statusA | Check whether the configured Hermes CLI runtime is available without running a provider request. |
| hermes_submitA | Start a long Hermes plan, draft, or approval-preview job and return immediately. Direct execute requests are converted to request-approval; use hermes_prepare and hermes_approve for execution. |
| hermes_job_statusA | Read lifecycle metadata for an asynchronous Hermes job without returning its output. |
| hermes_resultA | Read the bounded stdout/stderr result of a completed asynchronous Hermes job. |
| hermes_cancelC | Idempotently cancel a queued or running asynchronous Hermes job. |
| hermes_prepareA | Create a local, non-executing preview and short-lived one-shot approval ID without invoking Hermes or its tools. The caller must show preview.action to the human before approval. |
| hermes_approveA | Consume a prepared approval ID exactly once and submit the unchanged request for execution. This can cause external side effects. |
| hermes_rejectC | Consume a prepared approval ID without executing the external action. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
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.