Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

send_dm

Sends a direct message to a Discord user by ID, opening the DM when needed. Use it to deliver private messages, attachments, polls, or replies to a specific user.

Instructions

Send a direct message to a user by user ID (opens the DM if needed).

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": {
      "user_id": "<user_id>"
    },
    "name": "send_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttsNo
pollNoRaw poll object (or use create_poll)
filesNoFiles to attach (each: path, url or data_base64)
embedsNoEmbeds (bots/webhooks only)
silentNo@silent: send without notifications
contentNoMessage text (Markdown; mention users with <@id>, channels with <#id>, roles with <@&id>, custom emoji <:name:id>)
user_idYesUser ID
reply_toNoMessage ID (or link) to reply to
componentsNoComponents (bots only)
sticker_idsNoUp to 3 sticker IDs
mention_replyNoPing the author of the replied message (default true)
suppress_embedsNoHide link previews
allowed_mentionsNo{parse:["users","roles","everyone"], users:[], roles:[], replied_user}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 mutation and external-reach profile is covered. The description adds one genuinely useful behavioral fact beyond that — the DM channel is created on demand as a side effect — but says nothing about permissions, rate limits, or the bot/webhook-only restrictions on embeds and components.

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 front-loaded sentence with the action, the target, and the implicit channel-creation caveat; nothing is wasted. It is arguably under-specified for a 13-parameter tool, but there is no filler or redundancy to trim.

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 13-parameter, nested-object mutation tool with no output schema, the description is thin: it does not say what a successful send returns (message object?) or flag that several parameters are bot/webhook-only. The rich schema compensates for most of this, leaving the description adequate but not complete.

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 description coverage is 92% across 13 parameters, so the schema carries nearly all parameter meaning, including the Markdown mention syntax and file attachment options. The description only reinforces user_id and the message concept, adding no syntax or format detail beyond what the schema already provides.

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 states a specific verb and resource ("Send a direct message") and scopes it to a target ("to a user by user ID"), which implicitly separates it from group-DM and channel-message tools. It does not explicitly name a sibling such as send_message or create_group_dm, so differentiation is inferable rather than stated.

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 implied rather than prescribed: you use it to DM a user, and the parenthetical "(opens the DM if needed)" hints that a prior open_dm call is unnecessary. There is no explicit when-to-use versus send_message/create_group_dm guidance and no stated prerequisites or failure conditions.

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