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_publishC | 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
Tools are mostly distinct: publish vs poll vs review vs approve/reject are clearly separated, and lockdown tools (acquire/status/release/renew) are distinguishable. Minor potential overlap between poll and review for fetching events, but descriptions clarify that review shows hidden pending events.
Consistent 'agentbus_' prefix with verb_noun patterns for most tools (e.g., lock_acquire, lock_release, lock_renew). Deviations like 'approve' and 'reject' use a single verb, but they remain readable and fit the domain.
10 tools are well-scoped for an agent bus handling event approval, polling, publishing, and lock leasing. Each tool appears to serve a distinct purpose with no redundancy.
Covers the full lifecycle: publish, poll, review, approve/reject, status, and lock management (acquire, status, renew, release). No obvious gaps for the stated event bus and lock leasing domain.