agent-coordination-mcp-server
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 |
|---|---|
| create_roomA | Create a coordination room for agents to collaborate. Rooms are persistent spaces where agents share context, coordinate tasks, and exchange results. Args: room_id: Unique room ID (e.g. "project-alpha", "data-pipeline") name: Display name for the room description: What this room is for created_by: Agent or user who created the room |
| join_roomC | Join a coordination room. Args: room_id: Room to join agent_id: Your agent identifier |
| send_messageA | Send a message to a coordination room. Share context, results, status updates, or requests with other agents in the room. Args: room_id: Target room sender: Your agent identifier message: The message content message_type: Type: "text", "result", "request", "status", "context" metadata: Optional JSON metadata |
| read_messagesA | Read messages from a coordination room. Get the latest messages or messages since a specific time. Args: room_id: Room to read from limit: Max messages (default: 20) since: Only messages after this ISO timestamp (optional) |
| list_roomsA | List all coordination rooms. Args: active_only: Only show active rooms (default: True) |
| share_contextA | Share a piece of context/data with a room. Structured way to share results, findings, or data points that other agents in the room can reference. Args: room_id: Target room sender: Your agent identifier key: Context key (e.g. "api_results", "analysis", "decision") value: The context value (text or JSON string) |
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 6 tools
Each tool has a distinct purpose: room creation, joining, listing, message reading, message sending, and context sharing. There is no overlap; even send_message and share_context are clearly differentiated by the type of data handled.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_room, send_message), making them predictable and easy to understand.
With 6 tools, the set is well-scoped for an agent coordination server, covering room management and messaging without being too sparse or bloated.
Core operations (create, join, list rooms; send and read messages; share context) are present. A notable gap is the lack of a leave_room or delete_room tool, but the surface is otherwise complete for typical coordination workflows.