Covalent Bond
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COVALENT_RELAY_URL | No | The URL of the relay server. Default: https://covalent-bond-relay.gopalrajsuresh.workers.dev | https://covalent-bond-relay.gopalrajsuresh.workers.dev |
| COVALENT_MAX_FILE_KB | No | Maximum file size in KB for transfers. Default 256, max 384. | 256 |
| COVALENT_NOTIFICATIONS | No | Set to 'off' to disable desktop notifications. | on |
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 |
|---|---|
| bond_connect | Create a new Covalent Bond session and get a shareable session code. The other agent will use this code to join. |
| bond_joinA | Join an existing Covalent Bond session using a session code (format: XXXX-XXXX-XXXX Base58, e.g., "3KPz-QR7m-8WXn"). Call this when the user provides a session code from another agent. The code is a shared secret - it authenticates the encrypted channel and is never sent to the relay. |
| bond_sendA | Send a file to the connected agent. File will be encrypted and delivered with an optional message. Subject to 10-second rate limit and security validation (file type whitelist, 256KB default size limit, configurable via COVALENT_MAX_FILE_KB). |
| bond_acceptA | Accept a pending file transfer. File will be written to ~/.covalent/incoming/ and its content returned, wrapped in untrusted-data markers. |
| bond_declineA | Decline a pending file transfer. File will be discarded and sender will not be notified. |
| bond_message | Send a short encrypted text message to the connected agent (no file involved). Use this for agent-to-agent conversation: questions, context, summaries. Requires a confirmed session. Max 4000 characters. |
| bond_wait | Wait (long-poll) until the next event arrives from the peer (a message, incoming file, or disconnect) or until the timeout passes. Use this in a loop to hold a live conversation with the other agent: call bond_wait, react to what it returns, reply, call bond_wait again. Returns immediately if events are already queued. This costs tokens per call, so loop only during an active conversation; for idle waiting rely on desktop notifications and bond_status. |
| bond_status | Get current Covalent Bond connection status: session info, handshake state, pending file transfers, and any events (incoming transfers, peer messages) that arrived since the last tool call. Call this periodically while connected to pick up incoming transfers. |
| bond_endA | End the current Covalent Bond session and disconnect from relay. Clears all pending transfers. |
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 clear, distinct purpose: joining a session, sending a file, accepting/declining a transfer, and ending the session. No overlapping functionality.
All tools follow a consistent 'bond_verb' pattern (e.g., bond_join, bond_send), making it predictable and easy to understand.
With 5 tools, the server covers the essential operations for a file transfer session without being excessive or sparse.
The set covers the core session lifecycle (join, send, accept/decline, end), but lacks a tool to create a new session or view pending transfers, which are minor gaps.