Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_BUS_FILEYesAbsolute path to the shared room JSONL file used by all clients.
AGENT_BUS_TOKENNoOptional token for Bearer authentication of HTTP requests.

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bus_sendA

Send a message to the shared room. Set 'to' to address specific roles; leave it empty to broadcast to everyone.

bus_readB

Read messages newer than an id cursor, optionally filtered by recipient, sender, or tags.

bus_waitB

Long-poll until a matching message arrives. Defaults to messages broadcast or addressed to this role, excluding its own.

bus_historyC

List archived rooms, or replay one by name when 'archive' is given.

bus_searchA

Search the room, and optionally its archives, by text, sender, or tag.

bus_exportA

Export the current or last audit session as a Markdown review record, covering every message since it was opened.

bus_whoA

Show live roles and MCP processes in the room.

bus_openC

Open an audit session after stating its measurable ceiling.

bus_closeA

Close the active audit session and record its outcome.

bus_resetB

Archive the active room and begin a new conversation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct action: searching, reading, waiting, sending, session management, room reset, history, and role discovery. The overlapping message retrieval tools (read, wait, search) are clearly differentiated by their behavior (pull, long-poll, search).

Naming Consistency4/5

All tools share the bus_ prefix with a short action verb. bus_who and bus_history are less verb-like but still follow the concise command-style pattern, and no style mixing (all lowercase, snake_case). Slight inconsistency in verb vs. noun, but overall predictable.

Tool Count5/5

10 tools for a room-based messaging and audit system is well-scoped. Each tool covers a distinct capability with no redundant duplicates.

Completeness5/5

The set covers the full messaging lifecycle (send, read, wait), search, history, audit session lifecycle (open, close, export), room reset, and participant discovery. No obvious dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues