Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_MAIL_DIRNoSet AGENT_MAIL_DIR to move the mailbox, for example into a project folder.

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
mail_sendA

Deliver a text message from you ("agent") to another coding agent's inbox, for example to hand off a task, ask a question or report a result. Call mail_peers first if you are unsure of the recipient name. To answer a message you received from mail_check, pass its id as reply_to. Each call writes one new message and never edits or removes existing mail. If the recipient has not started yet, the message waits in its inbox. Returns "sent to "; keep the id if you expect a reply that references it.

mail_checkA

Fetch the unread messages addressed to you ("agent"), oldest first. Use it when you expect a reply or want to see if another agent wrote to you. Reading consumes the messages: each one is moved to your read folder and is not returned again, so act on or note what you need. With wait_seconds above 0 the call blocks until at least one message arrives or the time runs out. Returns each message as "[] from (re ) at :" followed by its body, or "no new messages". When live push is installed, new mail may already appear in your session without calling this tool.

mail_peersA

List every agent name that has a mailbox here, so you know valid recipients for mail_send. Read-only: it changes nothing. Returns one line per agent: " - last started ", or "never started" for an agent that has mail waiting but has not run yet. Your own name is marked "(you)". A recent start time suggests the agent is active, but it does not guarantee a session is open right now.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

The three tools map to clearly distinct actions: sending mail, checking/consuming inbox, and listing available peers. There is no overlap—mail_send writes, mail_check reads, and mail_peers is explicitly read-only. An agent can pick the right tool without hesitation.

Naming Consistency5/5

All tools follow the exact same mail_<verb> pattern: mail_send, mail_check, mail_peers. The convention is predictable, readable, and consistent throughout.

Tool Count5/5

Three tools exactly cover the minimal inter-agent mail model: send, receive, and discover recipients. There is no redundancy and no obviously missing core operation for this scope.

Completeness4/5

Core lifecycle is covered—compose/send, read/consume, and recipient discovery. Minor gaps exist: there is no tool to retrieve previously read (consumed) mail or view a sent/outbox history, though agents can work around this by acting on messages immediately or saving IDs.

Maintenance

ActivityNo data
ResponsivenessResponsive