Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_reply_dm

Reply to any message in a DM conversation with a quoted reference, even if it was sent by the bot or the user, and receive the new message ID.

Instructions

Reply to a specific message in a DM, attaching a quoted reply reference. Unlike the edit/delete DM tools, this works on any message in the conversation (the bot's or the user's). Use discord_send_dm for a standalone DM with no reference. Returns the new reply's message ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesPlain-text body of the reply (max 2000 characters).
user_idYesDiscord user ID (snowflake) of the DM recipient.
message_idYesID of the target message within the DM conversation.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already signal a non-read, non-destructive write operation, so the bar is lower. The description adds useful behavioral context beyond annotations: the quoted-reply reference behavior, the fact that the target can be the bot's or the user's message, and the return value (new reply's message ID). It does not discuss failures or rate limits, but the added context is meaningful.

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?

Three sentences with zero waste: core behavior, sibling differentiation, alternative routing, and return value. The most important scoping constraint is front-loaded in the first sentence, and every sentence earns its place.

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

Completeness4/5

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

For a 3-parameter tool with rich schema descriptions and annotations, the description is nearly complete: it covers behavior, quoting, message scope, alternatives, and return value. The only gap is not explicitly distinguishing from discord_reply_message (the guild-message counterpart), though the DM scope is inherent in the tool name and description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying message_id semantics — that the target can be 'any message in the conversation (the bot's or the user's)' — which is not stated in the schema. It also states that content is a plain-text reply body, consistent with the schema's max-2000-character constraint.

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 states a specific verb+resource: 'Reply to a specific message in a DM, attaching a quoted reply reference.' It distinguishes from sibling DM tools (edit/delete/send) by noting it works on any message and that send_dm is for standalone messages with no reference. The purpose is immediately clear.

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?

Explicit when-to-use guidance is provided: 'Unlike the edit/delete DM tools, this works on any message in the conversation... Use discord_send_dm for a standalone DM with no reference.' This names alternatives and the condition that selects this tool, leaving nothing to inference.

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