Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

reject_message_request

Destructive

Reject and delete a Discord DM message request by channel ID, removing it from your direct message requests.

Instructions

Reject (delete) a DM message request. [DELETE /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": "reject_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.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description contributes the clarifying parenthetical '(delete)', which tells the agent the request is removed rather than merely marked declined, and the endpoint spelling out that it targets the caller's own recipient record (@me). It says nothing about reversibility or whether the sender is notified.

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?

One sentence plus an endpoint tag, with the operation and resource front-loaded and zero filler. Nothing could be cut without losing information.

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 destructive tool with annotations and no output schema, the definition covers the essentials. It stops short of explaining post-condition behavior (whether the request can be recovered, whether it affects the sender's ability to re-request), which matters for an irreversible operation.

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?

Single required parameter with 100% schema description coverage, so the schema already documents channel_id fully. The description adds no format or constraint detail beyond what the schema provides; baseline 3 applies.

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 (reject/delete) and resource (DM message request), plus the underlying endpoint DELETE /channels/{channel_id}/recipients/@me, which pins down exactly what is being removed. It does not explicitly name accept_message_request or batch_reject_message_requests as the contrasting operations, so sibling differentiation relies on the reader's inference.

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?

There is no stated guidance on when to reject versus accept a request, nor when to use this single-item tool instead of the batch variant. The only usage signal is the implied semantics of the word 'reject' itself.

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