MCP control plane for Hermes Agent durable runs and optional shared live sessions
19 tools with complete descriptions (194 - 392 chars, well above 10-char minimum) and clear verb-noun naming (run_*, live_*, session_*, bridge_*). All tools have input schemas with typed parameters and descriptions. However, output schemas are entirely undocumented, no tool specifies what fields or structure the response contains. Parameter descriptions are present but often dense and assume deep domain knowledge of Hermes internals (profile routing, lane inference, idempotency semantics). No enum constraints on string parameters (profile, lane, session_id are free-form). Error handling is mentioned in descriptions ('fail closed', 'lane_profile_ambiguous') but no recovery guidance is provided. Missing: pagination parameters, result limits, and chaining IDs in responses. Composition is strong (each tool has one clear responsibility), but descriptions are optimized for Hermes experts, not LLM selection.
Run non-consuming Hermes health, models, and capabilities probes. Optional profile probes through that profile's prefix.
Read bounded live TUI events after an optional per-session sequence cursor. Optional profile follows live_status inference. When supplied explicitly, session_id is the runtime ID; prefer lane instead of copying a stored ID.
Report live TUI connection, auth-mode, bounded-buffer, and replay state without an LLM turn.
Read exact live TUI session history for recovery/reconciliation. Optional profile follows live_status inference. When supplied explicitly, session_id is the runtime ID; prefer lane.
Interrupt the exact live TUI session cooperatively. Optional profile follows live_status inference. When supplied explicitly, session_id is the runtime ID; prefer lane.
Output schemas completely undocumented. No tool specifies response structure, field types, or what data is returned. LLMs cannot plan downstream calls or extract required fields.
No enum constraints on string parameters (profile, lane, session_id, request_id). Free-form strings invite hallucinated values. LLMs cannot self-correct without explicit valid options.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Submit one prompt to a live TUI session; never retries an unknown acknowledgement. Optional profile follows live_session_open inference; the profile is carried on the submit and stored with the request. When supplied explicitly, session_id is the runtime ID; prefer lane instead of copying a stored ID.
Reconcile an unknown live prompt against post-boundary durable history (pre-submit row cursor) without resubmitting it; the request's stored profile governs and no profile argument is accepted. Ambiguous matches stay unknown.
Reconnect the live TUI WebSocket and replay retained per-session events; every remembered (profile, lane) reopens under its stored profile. Needs no profile argument.
Connect to the existing Hermes TUI WebSocket and create or resume one durable session lane under a profile. Optional profile: supplied names the (profile, lane) binding exactly; omitted infers an exact known stored session's profile first, otherwise the lane's single bound profile; ambiguous known identities fail with lane_profile_ambiguous, and a genuinely unbound new lane uses the default profile. Here session_id is the stored/durable ID to resume; the response session_id is the runtime ID and stored_session_id is the durable ID. Prefer lane for subsequent reads and control calls.
Read exact live TUI session status without submitting a prompt. Optional profile: omitted infers the lane's or stored session's single bound profile (fail-closed when ambiguous); when supplied explicitly, session_id is the runtime ID; prefer lane.
Queue exact-session live TUI steering text. Optional profile follows live_status inference. When supplied explicitly, session_id is the runtime ID; prefer lane instead of copying a stored ID.
Wait for this request's own live completion with a bounded timeout. The request's stored profile governs; a supplied different profile conflicts. Lane-addressed waits infer the profile and fail closed when ambiguous. Shared-session ownership is proven via gateway inflight evidence; unprovable or foreign-turn cases return conservative ambiguous_turn/completion_not_observed states instead of another client's answer.
Collect the live SSE events retained for one exact Hermes run. Optional profile follows run_status semantics.
Start one idempotent Hermes durable run in a named lane. Optional profile routes the run through that profile's /p/<profile>/ API and credentials. When omitted, an exact existing request/idempotency/session identity or one unambiguous existing lane profile is inferred; only a genuinely new unbound admission defaults to the default profile. An explicitly supplied conflicting profile fails closed instead of rerouting.
Read status and terminal output for one exact Hermes run. Optional profile must match the run's stored profile; lane-only lookups infer the profile and fail closed if the lane exists under multiple profiles.
Queue course correction for one exact running Hermes run. Optional profile follows run_status semantics.
Request cooperative stop for one exact Hermes run. Optional profile follows run_status semantics.
Poll one Hermes run until terminal or until the bounded wait expires. Optional profile follows run_status semantics.
Read bounded durable message history for one exact Hermes session. Optional profile routes through that profile's /p/<profile>/ prefix; omitted infers the session's locally known profile (fail-closed when ambiguous) and otherwise uses the default profile.
Error handling mentions failure modes (lane_profile_ambiguous, conflict errors) but provides no recovery guidance. Descriptions state what fails but not what the LLM should do next.
Descriptions assume deep Hermes domain knowledge (profile routing inference, lane binding semantics, idempotency key vs request_id distinction). Not optimized for LLM selection without Hermes expertise.
No pagination, result limits, or chaining IDs documented. Tools like run_events, session_history, live_events, live_history may return unbounded results, risking context window exhaustion.