agentbus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTBUS_AUTH | No | Set to 'off' to disable authentication | |
| AGENTBUS_TOKEN | No | Authentication token for publish calls (recommended) | |
| AGENTBUS_WORKSPACE | Yes | Path to the workspace directory | |
| AGENTBUS_PRODUCER_ID | No | Identifier for the agent (used when publishing events) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agentbus_publishB | Append one event to the workspace event log. |
| agentbus_pollA | Fetch events after cursor (at-least-once delivery). |
| agentbus_statusB | Workspace bus health and topic list. |
| agentbus_reviewA | List events pending human approval (hidden from standard poll). |
| agentbus_approveC | Approve a pending event so agents can see it on poll. |
| agentbus_rejectB | Reject a pending event and notify the originating agent. |
| agentbus_lock_acquireC | Acquire an exclusive advisory lease on a workspace resource. |
| agentbus_lock_releaseB | Release a held lease (idempotent if already expired). |
| agentbus_lock_renewC | Extend TTL on an active lease (heartbeat). |
| agentbus_lock_statusB | Check lock state without acquiring (no auth required). |
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 10 tools
Each tool has a clearly distinct purpose: publishing vs polling events, reviewing/approving/rejecting pending events, and lock status/acquire/release/renew are all separate actions. No two tools overlap in function.
All tools use the 'agentbus_' prefix consistently, but the verb/noun order is not uniform. Event-related tools are verb-only (publish, poll, review), while lock tools use noun-first (lock_acquire, lock_release) and status tools are noun-only (status, lock_status). Despite this, the naming is still predictable and readable.
10 tools is well-scoped for the domain of an agent communication bus. It covers the core event lifecycle (publish/poll), human approval workflow (review/approve/reject), and advisory locking (acquire/release/renew/status) without unnecessary bloat.
The tool set covers the full event bus lifecycle: publishing, polling, and health status. The approval workflow is complete with review, approve, and reject. Locking includes status, acquire, release, and renew, leaving no obvious gaps for the stated purpose.