agent-bus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AB_HOME | No | Points to a different bus directory (used for testing). | |
| AB_AGENT | No | Override for agent identity when AGENT_MAP.json rules cannot determine it. | |
| AB_SESSION_SLUG | No | Override for session slug when AGENT_MAP.json rules cannot determine it. | |
| AB_SESSION_TTL_MIN | No | Minutes without heartbeat before a session is considered dead. | 240 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bus_statusA | Who is on the bus and which sessions are live right now. Use before sending when an agent may have several sessions open, so the message reaches the workspace that is actually doing that work. |
| bus_inboxA | List pending messages for this session. By default: messages addressed to this workspace plus broadcasts to the agent. Other sessions' queues are left out unless all_sessions is set. |
| bus_readA | Read one message in full, including its payload and context refs. |
| bus_sendA | Send a message to another agent, or to one specific session of it. Prefer |
| bus_archiveA | File a message away so it stops blocking the session from closing. The Stop hook counts what is still pending, so archive each message once it is genuinely handled — not to silence the reminder. |
| bus_threadB | Replay a conversation in order: who said what, when. |
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 6 tools
Each tool has a clearly distinct responsibility: status for live sessions, inbox for pending messages, read for full message detail, send for delivery, archive for resolution, and thread for chronological replay. No two tools overlap in purpose or would cause an agent to misselect.
All tools follow a uniform bus_<action> pattern, making the API predictable and easy to navigate. The action terms are concise and match their functions.
Six tools is well-scoped for a message bus: enough to cover the full interaction lifecycle without redundancy. Each tool serves a distinct, necessary operation.
The set covers the core message lifecycle fully: send, receive, read, archive, inspect status, and replay threads. Broadcast delivery and per-session targeting are handled through bus_send, and archive provides a clean closure mechanism.