Skip to main content
Glama
phamviet86

codex-hermes-a2a-bridge

by phamviet86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hermes_task_get

Retrieve a task or its result from the Hermes A2A bridge, optionally acknowledging a consumed result ID with expected origin verification.

Instructions

Get a task/result; optionally acknowledge a consumed result_id with expected_origin verification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoRefresh a nonterminal task from Hermes when possible
task_idYesbridge_task_id or known A2A task id
expected_originNo
acknowledge_result_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / acknowledge_result_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Acknowledge Result Id"
+}
    • addedInput schema / properties / expected_origin
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Expected Origin"
+}
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=false and idempotentHint=false, so the agent already knows this is not a pure read. The description adds that acknowledgement is optional and that origin is verified, which explains the mutating profile, but it doesn't disclose what acknowledging actually does (marks consumed, irreversible?) or why the call is non-idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that leads with the core action and attaches the optional behaviour at the end. No wasted words, though the clause is packed tightly enough to be slightly cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. For a tool that mixes a read with an optional state-changing acknowledgement, the definition is adequate but leaves the acknowledge side-effect and sibling selection under-explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: task_id and refresh are documented in the schema, while expected_origin and acknowledge_result_id are not. The description partially compensates by naming both undocumented parameters and their roles (consumption, origin verification), which is the baseline for this coverage level, but it gives no format or matching semantics for expected_origin.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb+resource: 'Get a task/result' names both the action and the object, and the acknowledgement clause signals the consumption semantics. It does not, however, distinguish itself from siblings like hermes_task_wait, hermes_tasks_list, or hermes_task_cancel, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description hints at a retrieve-then-acknowledge flow ('optionally acknowledge a consumed result_id'), which implies one usage scenario, but it never states when to use this tool versus hermes_task_wait or hermes_tasks_list, nor any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools