Skip to main content
Glama
AceDataCloud

MCP Discord Bot Server

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

discord_send_dm

Send a direct message to a Discord user by providing their user ID and message content. Returns sent message details.

Instructions

Send a direct message (DM) to a Discord user.

Args:
    recipient_id: The Discord user ID to send the DM to.
    content: The text content of the direct message.

Returns:
    JSON object with the sent message details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe text content of the direct message. Required.
recipient_idYesThe Discord user ID of the recipient. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It confirms the operation is a send and that a JSON result is returned, but says nothing about bot permissions, whether the bot must share a guild with the recipient, rate limits, or failure modes when DMs are closed — significant omissions for an external-facing write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single-sentence summary is front-loaded and clear, but the Args block duplicates schema descriptions that already exist and the Returns line is redundant given the output schema exists. Some content does not earn its place.

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?

The output schema covers return values, so the description need not explain them and the Returns line is unnecessary. The missing pieces are operational: permission requirements and whether a DM channel must pre-exist, which leave the definition merely adequate.

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%, so both parameters are already documented in the schema. The Args section merely restates recipient_id and content verbatim without adding format, ID-source, or length-limit guidance, so 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 and resource ('Send a direct message (DM) to a Discord user'), which is clear. However, it never contrasts itself with the sibling discord_send_message (channel message) or discord_create_dm, so the agent must infer the distinction from the name alone.

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 when-to-use guidance, no prerequisites, and no mention of the sibling discord_create_dm, which an agent might reasonably need to call first to open a DM channel. Usage is only implied by the tool name.

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