Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

wait_for_event

Read-only

Waits for a specified Discord gateway event type and returns it when received, with optional user, guild, channel filters and timeout.

Instructions

Wait for any gateway event type (e.g. MESSAGE_REACTION_ADD, RELATIONSHIP_ADD, CALL_CREATE, GUILD_MEMBER_ADD, VOICE_STATE_UPDATE).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "types": "<types>"
    },
    "name": "wait_for_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesYes
user_idNo
guild_idNo
channel_idNo
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and non-destructive, so the safety profile is covered. The description adds that the tool waits on external gateway events, which explains the open-world hint, but never states that the call blocks, what happens on timeout, or whether it returns a single event or an array.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the actionable content front-loaded and no wasted phrasing. It is efficient but spends its entire budget on examples rather than on semantics the schema cannot supply.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A no-output-schema wait tool with four undocumented filter/timeout parameters needs more than a list of event names. The definition is adequate to start a call with types only, but an agent cannot confidently use the scoping or timeout parameters from this description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, and the description only clarifies the required types array via examples. The user_id, guild_id, channel_id, and especially timeout_seconds parameters get no meaning at all, leaving the blocking/timeout contract unstated where it matters most.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and resource ("Wait for any gateway event type") and supplies five concrete event-name examples, so the agent knows exactly what class of input is expected. It does not distinguish itself from the sibling wait_for_message, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over wait_for_message, nor on prerequisites, concurrency, or whether multiple waits can be outstanding. The word "any" weakly implies broadness versus a message-specific sibling, but the agent is left to infer the routing decision entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools