Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

accept_message_request

Accept a pending Discord DM message request by channel ID to approve the conversation and allow direct messaging.

Instructions

Accept a DM message request. [PUT /channels/{channel_id}/recipients/@me]

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": {
      "channel_id": "<channel_id>"
    },
    "name": "accept_message_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

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 declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the HTTP endpoint, which usefully signals idempotent PUT semantics and that the action targets the current user (@me). It does not explain what happens afterward (whether a DM channel opens, history visibility, or whether the request record is consumed).

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?

Two short fragments with the action front-loaded and the endpoint as supporting detail; nothing is padding. Slightly terse rather than over-written.

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?

For a one-parameter mutation with annotations and no output schema, the definition is minimally sufficient to invoke correctly. It falls short on post-call effects and on distinguishing the accept/reject pair, which are the main open questions an agent would have.

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

Parameters3/5

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

Schema coverage is 100% and the single channel_id parameter is fully documented in the schema, so the baseline is 3. The description only restates channel_id implicitly through the path template and adds no format or selection guidance beyond the schema.

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?

States a specific verb and resource ('Accept a DM message request') and pairs it with the underlying endpoint, so an agent can tell this mutates a pending DM request rather than a friend or guild join request. It lacks explicit differentiation from reject_message_request, but the action itself is unambiguous.

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 call this versus reject_message_request or accept_friend_request, and no prerequisites such as requiring an existing pending request. Usage is only inferable from the verb 'accept' and the DM qualifier.

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