Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_send_dm

Send a private direct message to a Discord user by their user ID. Use when you need to message a user directly instead of posting to a channel.

Instructions

Send a private direct message to a user by their user ID. Use discord_send_message to post in a server channel instead. Requires the bot to share at least one server with the user, and the user must allow DMs from server members (otherwise Discord rejects the send). Returns the new message ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesPlain-text body of the DM (max 2000 characters).
user_idYesDiscord user ID (snowflake) of the DM recipient.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / user_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed2 schema fields changedv1.6.0
    • changedInput schema / properties / content / description
      Previous value: -"The message content to send."New value: +"Plain-text body of the DM (max 2000 characters)."
    • changedInput schema / properties / user_id / description
      Previous value: -"The Discord user ID."New value: +"Discord user ID (snowflake) of the DM recipient."
  4. Addedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses the failure mode (Discord rejects the send if DMs are not allowed), the prerequisite of sharing a server, and the return value (new message ID). Annotations only indicate read-only, idempotency, and destructive hints, so this extra behavioral context is valuable.

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?

The description is three sentences with no wasted words. The primary action is front-loaded, the sibling alternative is given immediately, and the prerequisites and return value each earn their place.

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

Completeness5/5

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

For a simple two-parameter send action with no output schema, the description covers the essential context: what it does, when to use the alternative, the failure conditions, prerequisites, and what the caller gets back. Nothing critical is missing.

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 100%, and both parameters are already well documented in the schema: user_id as a Discord snowflake and content as max-2000-character plain text. The description adds only minimal extra meaning, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Send a private direct message to a user by their user ID.' It clearly distinguishes this tool from the sibling discord_send_message by explicitly noting that discord_send_message is for server channels.

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

Usage Guidelines5/5

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

It explicitly tells the agent to use discord_send_message instead when posting in a server channel, and it states the preconditions for success: the bot must share a server with the user and the user must allow DMs from server members. This gives clear when-to-use and when-not-to-use guidance.

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