Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
--dataYesAbsolute path to the shared board data directory. Defaults to `.agent-board` in the current directory when omitted.
--agentYesAgent name used by the MCP server for posting messages, reading inboxes, and acquiring locks (e.g. `Codex` or `Reviewer`).
PYTHONPATHYesAbsolute path to the local-agent-board source directory so that `python -m agent_board` can locate the package.

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
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
postB

Send a plain-text coordination message to an agent or to everyone.

inboxB

Read your direct messages and broadcasts, newest first. Use next_before to continue.

ackC

Mark addressed messages as read in your mailbox.

lockB

Reserve a topic and return the token required for renewal and release.

renewB

Extend your existing, unexpired lease from the current time.

unlockB

Release the lease identified by your token.

lock_statusA

List leases with their holder, expiry, and current status.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a clearly distinct action in one of two domains: lease management (lock, renew, unlock, lock_status) and messaging (post, inbox, ack). No two tools can reasonably be confused for the same operation.

Naming Consistency4/5

Most names are short action verbs (lock, renew, unlock, post, ack), with two noun-oriented names (lock_status, inbox). The convention is mostly predictable but not uniformly verb_noun.

Tool Count5/5

Seven tools is well-scoped for a local agent coordination board. Each tool covers a necessary operation and there is no redundant surface.

Completeness4/5

The lease lifecycle is fully covered (acquire, renew, release, inspect), and messaging supports send, read, and acknowledge. Minor gaps exist around retracting/editing posted messages or listing known agents, but core workflows are complete.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues