Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

batch_reject_message_requests

Reject multiple Discord direct-message requests at once by providing channel IDs, clearing pending DM requests in bulk.

Instructions

Reject several DM message requests. [PUT /channels/recipients/@me/batch-reject]

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_ids": "<channel_ids>"
    },
    "name": "batch_reject_message_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idsYesChannel IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description contributes only the raw HTTP endpoint line, saying nothing about whether rejections can be undone, whether senders get notified, or what happens to existing requests — no behavioral value beyond structured fields.

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 clauses: the action comes first and the endpoint reference trails it. Nothing is padded, though the bracketed HTTP route is arguably redundant detail for an agent choosing a tool.

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 batch mutation with no output schema, the definition covers what the tool does and which endpoint it hits. It omits what happens after rejection (state changes, reversibility) and any batch-size constraint, leaving the agent with enough to call it but not enough to predict consequences.

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?

With one parameter at 100% schema description coverage, the schema already defines channel_ids. The description adds no format, ordering, or size guidance for those IDs, so the baseline of 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') and resource ('DM message requests') with the batch scope made explicit by 'several'. The plural 'several' implicitly distinguishes it from the singular reject_message_request sibling, though that sibling is never named.

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?

Usage is only implied: the word 'several' suggests this is the multi-item variant and the single-item sibling should be used for one request. There is no explicit 'use this when...' statement, no batch-size limits, and no exclusion of alternatives.

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