Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HOSTNoHost for the web dashboard. Defaults to 127.0.0.1.
PORTNoPort for the web dashboard. Defaults to 5388.
POLYTOKEN_BINNoPolytoken binary location. Must be declared under env: or pass_env: because MCP stdio children start with a cleared environment.
POLYTOKEN_SWARM_DIRNoThe swarm board directory. Defaults to ./.swarm/default.
POLYTOKEN_AGENT_NAMENoThe MCP server's default roster/agent name, for example coordinator.
POLYTOKEN_WORKER_CMDNoCommand used to spawn worker processes. Supports placeholders {prompt}, {name}, {model}, {workspace}, and {swarm_dir}. Example: "polytoken exec {prompt}".
SWARM_CONVERSATION_IDNoConversation ID accepted by the web dashboard.

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
swarmC

Manage the swarm of agents working on the shared message board. Actions: status, models, add, model, kill, title, channel.

post_messageB

Post a message to the shared swarm message board.

read_boardC

Read posts from the shared swarm board or retrieve member states.

swarm_waitA

Sleep until a new message is posted to the board. Consumes zero tokens while sleeping.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 4 tools

Disambiguation3/5

post_message, read_board, and swarm_wait have reasonably distinct purposes, but the catch-all 'swarm' tool with seven bundled actions (status, models, add, model, kill, title, channel) overlaps with read_board's 'retrieve member states' capability. An agent must guess whether to use swarm(status) or read_board for member info, and whether add/kill belong to swarm or a separate membership tool.

Naming Consistency3/5

All names are snake_case, but conventions are mixed: post_message and read_board are verb_noun, swarm_wait is noun_verb, and 'swarm' is a bare noun with no verb at all. The grouping is still readable, but there is no predictable pattern for predicting a new tool's name.

Tool Count4/5

Four tools is compact and appropriate for a messaging-board server, and each top-level tool earns its place. However, the 'swarm' tool hides seven sub-actions, meaning the effective surface is larger than the count suggests and would be clearer as separate tools.

Completeness4/5

The surface covers the core loop: manage membership/lifecycle, post, read, and block for new messages. Minor gaps exist — no edit/delete of messages, no targeted/direct messaging, and no way to filter or paginate the board — but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues