a2a-raid-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 |
|---|---|
| raid_connectA | Connect to your Agent Raid seat over standard A2A. Flow: raid_connect -> raid_wait_turn -> SHOW the returned turn/menu to your
human and WAIT for their actual choice -> raid_play(their choice) -> repeat
raid_wait_turn/raid_play until the game is over. Call raid_poll_chat between
turns to catch up on party room-chat. |
| raid_wait_turnA | Wait for your next turn's prompt, bounded by |
| raid_playA | Submit your human's chosen move for the CURRENT pending turn (call raid_wait_turn first to see it, show it to them, and get their actual choice — never invent a move yourself). Returns immediately; call raid_wait_turn again for the next turn. |
| raid_poll_chatA | Best-effort peek at party room-chat since the last poll (safe to call between turns, or instead of a turn while waiting). Returns one ": " line per new message, or "(no new party chat)" if nothing's new. |
| raid_sayA | Send a party-chat line to the raid at ANY time (not just on your turn). Use this to relay what the human trainer wants to tell the team. The message appears in every player's Room chat immediately. Call this whenever the human has something to say to the party between turns. |
| raid_leaveA | Leave the raid: cancel the background driver and close the session cleanly. Safe to call even if not connected. |
| raid_statusA | A quick snapshot of session state: connected? a turn pending? game over? any error? Useful to re-orient after a gap in the conversation. |
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
Each tool has a clearly distinct role: connect, wait for turn, play move, poll chat, send chat, leave, and status. No two tools overlap in purpose or behavior, so an agent can confidently select the right one for each action.
All tools follow the same verb_noun pattern with 'raid_' prefix (raid_connect, raid_wait_turn, raid_play, etc.), and verbs are consistently descriptive. The naming is perfectly predictable and uniform.
Seven tools cover the full lifecycle of a raid session without bloat. Each tool is necessary for the core flow (connect, wait, play) or supplementary features (chat, status, leave), and none feel redundant.
The tool surface covers connection, turn-taking, move submission, party chat, status checks, and graceful exit. The only minor gap is lack of a dedicated history or replay tool, but the core workflow is fully supported.