Skip to main content
Glama
onicarps

agentbus

by onicarps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agentbus_publish

Append a structured event to a shared workspace event log, using topic, payload, and optional trace metadata to coordinate multi-agent workflows.

Instructions

Append one event to the workspace event log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYes
actionNo
payloadYes
trace_idNo
auth_tokenNo
producer_idNo
causation_idNo
parent_span_idNo
schema_versionNo1.0
idempotency_keyNo
sla_timeout_minutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.0
    • addedInput schema / properties / action
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Action"
+}
  2. Addedv0.18.0
  3. Removedv0.17.0
  4. Addedv0.16.3
  5. Removedv0.16.3
  6. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / parent_span_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Parent Span Id"
+}
    • addedInput schema / properties / trace_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Trace Id"
+}
  7. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / sla_timeout_minutes
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sla Timeout Minutes"
+}
  8. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Append' implies a durable mutation, but the description says nothing about authentication (despite an auth_token parameter), idempotency/deduplication behavior (despite an idempotency_key parameter), ordering guarantees, or failure modes.

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

Conciseness3/5

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

A single clean, front-loaded sentence with no filler, which is structurally good. But for an 11-parameter mutation tool the extreme brevity reflects under-specification rather than disciplined conciseness.

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

Completeness2/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 needn't be explained, but the description leaves the auth requirement, idempotency semantics, and event-schema/versioning behavior unspecified for a complex write tool with no annotations and no parameter docs.

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

Parameters1/5

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

Schema description coverage is 0% across 11 parameters, and the description adds no parameter meaning at all. Critical parameters such as auth_token, idempotency_key, causation_id, parent_span_id, and sla_timeout_minutes are entirely undocumented in both places.

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?

The description gives a specific verb ('Append'), resource ('event log'), and scope ('one event', 'workspace'), so an agent can tell this is a write/publish operation. It does not, however, differentiate itself from siblings like agentbus_poll or agentbus_review, which an agent must distinguish on its own.

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?

There is no when-to-use guidance, no conditions selecting this over agentbus_poll or any other sibling, and no stated prerequisites. The agent must infer the entire usage context from the name alone.

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