Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

wait_for_message

Read-only

Waits for the next Discord message matching your filters—such as channel, author, mention, or text—and returns it within the timeout, so automation can pause until a qualifying reply arrives.

Instructions

Wait for the next incoming message (e.g. a reply) matching filters, up to timeout_seconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wait_for_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
containsNo
guild_idNo"@me" = any DM
author_idNo
channel_idNo
mentions_meNo
include_mineNo
timeout_secondsNoDefault 60, max 600

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description usefully adds the blocking-with-timeout trait. However, for a long-polling tool the critical behavior is undisclosed: what is returned when the timeout elapses (null, empty, error) and whether the call holds the connection for up to 600 seconds.

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

Conciseness5/5

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

A single sentence that front-loads the action, names the resource, and folds the filter and timeout qualifiers in without waste.

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

Completeness2/5

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

Seven parameters at 29% schema coverage, no output schema, and no description of the timeout outcome — the definition leaves the agent unable to predict the return value or the meaning of most filters, which is a serious gap for a blocking tool.

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 coverage is low at 29% (only guild_id and timeout_seconds are documented, the latter repeated in the description). Five filters — contains, author_id, channel_id, mentions_me, include_mine — get no explanation, so the agent cannot tell whether 'contains' is a substring match or exact, or what include_mine changes when waiting for 'incoming' messages.

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?

Specific verb and resource: 'Wait for the next incoming message (e.g. a reply) matching filters, up to timeout_seconds.' It makes clear this is a blocking wait rather than a fetch, which distinguishes it from get_message-style siblings, though it never names any sibling explicitly.

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

Usage Guidelines3/5

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

The parenthetical '(e.g. a reply)' implies the use case of waiting on a response, but there is no explicit when-to-use/when-not guidance and no mention of the obvious alternative wait_for_event, leaving the agent to infer which wait tool applies.

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