hoptell
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOPTELL_ENV | No | Path to a settings file to load environment variables from | |
| HOPTELL_HOME | No | Local state directory (default ~/.hoptell) | |
| HOPTELL_NAME | No | This agent's peer name (letters, digits, _ and -). Default <hostname>-<pid>. | |
| HOPTELL_PUSH | No | Push mode: 'channel' or 'listener', overrides detection | |
| HOPTELL_RELAY | Yes | Relay URL, ws://host:7777 or wss:// behind TLS | |
| HOPTELL_ROLES | No | Comma-separated roles for routing messages, e.g. reviewer,backend | |
| HOPTELL_TOKEN | Yes | Shared secret, or a member's own token |
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": true
} |
| experimental | {
"claude/channel": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_peersA | List hoptell peers (agent sessions on this or other machines) and whether they are online. |
| send_messageA | Send a text message to a named peer, or broadcast to @ or @all. Direct messages can be queued for known offline peers. Broadcasts target online peers only and are not queued for offline peers. Snapshot command: |
| wait_for_messageB | Wait for inbox messages up to timeout_seconds and return them. Use this only when this session's delivery instructions call for waiting. The wait can also end for a held-message notice or cancellation. Review a snapshot's supplied content; its file label is not a local path. Reply with review_request_id, based_on set to its sha256, and reply_to when available. Before using a local checkout, check the local file with check_snapshot (or run |
| read_inboxC | Return messages received from peers. Listener command (listener delivery only): |
| ack_messagesA | Acknowledge a handled message batch using its receipt. Unacknowledged messages may reappear after the configured acknowledgement timeout. |
| check_snapshotA | Check whether a local file in this session's folder still has a snapshot's sha256. It only reads that file and sends nothing. Use it for the --check step of the read_inbox and send_message descriptions. |
| read_diffA | Show the commits and the diff between two commits of the git repository in this session's folder, for a review. It runs git with no configured programs (hooks, filters, diff helpers, signature checks) and sends nothing. Use it instead of git log, diff or show in a shell. |
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 7 tools
The message-retrieval cluster (wait_for_message, read_inbox, ack_messages) has boundaries that are blurry, and the long cross-referential descriptions copy identical snapshot-review instructions into multiple tools, obscuring their distinct roles. send_message, check_snapshot, read_diff, and list_peers are clearly distinct, but the receive-side trio will cause occasional misselection.
All tools follow a verb_noun snake_case pattern (send_message, wait_for_message, check_snapshot, list_peers, read_diff, ack_messages). The only minor deviation is read_inbox using a noun other than 'message' while its siblings use 'message', a small inconsistency but still readable and predictable.
Seven tools is well-scoped for a peer messaging plus file-review protocol. Each tool maps to a needed operation (send, wait, read, ack, list peers, verify snapshot hash, inspect diff) with no obviously redundant entries.
The surface covers the messaging lifecycle (send/receive/acknowledge/peer discovery) and the review workflow (hash check, diff inspection). Coverage is solid; missing pieces like message history/search or an explicit file-send tool (currently delegated to the CLI snapshot command) are minor workarounds.