mesh
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MESH_DIR | No | Override the state directory path (default is .mesh/) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| registerC | Announce presence and refresh liveness (heartbeat). |
| rosterC | List known agents and their liveness. |
| claimC | Atomically acquire (or queue for) a resource lock. |
| releaseC | Relinquish a held claim or cancel a queued ticket. |
| claimsC | Inspect current locks and queues. |
| postC | Send a durable message (agent_id, * broadcast, or topic:). |
| inboxA | Peek pending messages without advancing the cursor. |
| readC | Advance the read cursor (acknowledge consumption). |
| gcA | Drop TTL-expired messages and sweep dead claims; returns reclaimed count. |
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 9 tools
Each tool targets a distinct operation: locking, inspecting, garbage collection, peeking, sending, reading, registering, releasing, and listing. Descriptions clearly differentiate them, with no overlapping purposes.
Most tool names are single-word verbs, but 'gc' is an abbreviation and 'roster' is a noun, introducing slight inconsistency. However, the pattern is largely predictable.
With 9 tools, the server covers essential operations for messaging and locking without superfluous tools. The count feels well-scoped.
The tool set provides full lifecycle for messages (post, read, inbox, gc) and locks (claim, claims, release), plus presence (register, roster). Minor missing features like explicit message deletion or broadcast-only send could be present but are not critical gaps given descriptions.