agent-channel-mcp
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 |
|---|---|
| joinA | Join a room and return identity, participants, waiter state, command, and client-specific launch instructions. On each new MCP connection, call once and start command exactly once when waiter is missing. A new connection with the same room and name takes ownership. |
| sendB | Send to one role, or omit to to broadcast to every other registered role. |
| renameC | Change your role name in the current room. |
| leaveA | Leave the current room, stop its waiter, and allow another join. |
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 4 tools
Each tool targets a distinct action in the room lifecycle: joining, sending messages, renaming, and leaving. There is no overlap in purpose; join's complexity does not confuse it with other operations.
All tool names are single imperative verbs in lowercase (join, send, rename, leave), following a predictable and consistent convention throughout.
Four tools is well-scoped for a basic agent channel. Each tool earns its place by covering a necessary room interaction without redundancy.
The surface covers join, send, rename, and leave, which is most of the chat lifecycle. An explicit message-retrieval tool is missing, but the join response points to a waiter process that likely delivers incoming messages.