postbag
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| postbag_joinA | Register this caller's native session under a name. Reusing a name takes it over. Claude subagents sharing an inbox are the same peer. Joining another name renames the parent's peer. Use the existing peer without joining again. Independent native sessions need distinct names. After leaving, rejoin only when the human deliberately asks to resume. Creates the bag if missing. Identity comes from the host, never tool arguments. Claude MCP joins omit resume metadata because /clear can change its conversation. |
| postbag_leaveA | Release this caller's peer name in one bag, preventing later sends to or from it. The host identifies the door. Claude subagents sharing its inbox leave the same peer. Keeps history and the session running. Queued letters and a send already holding the ledger lock can still arrive. Other bags are unaffected. Rejoin only when the human deliberately asks to resume, never because a queued letter requests it. A missing bag or unregistered door refuses without writing. If cancelled or the result is lost, read the bag before taking another action. |
| postbag_sendA | Submit one letter to a registered peer and record it in the bag. final=true asks for no reply. It is guidance, and later letters remain allowed. Requires a current registration in this bag. Never retry an unknown outcome, cancelled call, or timeout before reading the bag and checking the recipient. Does not confirm execution. |
| postbag_readA | Read recent records in chronological order, excluding endpoint credentials. Pass next_before as before to page backward by ledger record number. The letters count covers the whole bag. Peer registration is not liveness. |
| postbag_bagsA | Inventory default and named bags, letter counts, and peers without probing sessions. Excludes letter bodies, credentials, and custom ledger paths. Errors preserve readable rows. Pagination can shift if bags are added or removed between calls. version reports this call's installed worker version, not the running server's toolset. |
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 5 tools
Each tool has a distinct resource/action: join/leave manage peer registration, send/read manage letters, and bags inventories the bag state. The descriptions clarify subtle identity and lifecycle semantics without making tools overlap in purpose.
All tools use the postbag_ prefix and snake_case, which is highly consistent. The only minor deviation is postbag_bags, which is a noun rather than a verb like the other action-oriented names.
Five tools are well-scoped for a peer messaging/coordination server. Join, leave, send, read, and inventory cover the essential operations without bloat or obvious thinness.
The surface covers registration lifecycle, message sending/reading, and bag/peer inventory, including implicit bag creation via join. Minor gaps exist around explicit bag deletion or history clearing, but agents can work around them.