Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by tensakulabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_send_message

Send a message to a Discord channel or user via DM. Optionally reply to an existing message.

Instructions

Send a message to a channel or user (DM). Specify channelId OR userId.

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": {
      "content": "<content>"
    },
    "name": "discord_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdNoGuild channel ID
userIdNoUser ID to DM
contentYesMessage text
replyToMessageIdNoOptional message ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It adds the exclusive OR constraint on channelId and userId, but does not disclose permissions, rate limits, success/error behavior, or what happens if both parameters are supplied. This is adequate but not rich.

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 a single short sentence that is front-loaded with the primary action. Every word contributes value; there is no wasted text.

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?

Given 4 parameters and no output schema, the description adequately states the tool's purpose and key parameter constraint. However, it lacks explanations of success/error responses, rate limits, or prerequisites (e.g., bot must share a guild for DMs). This leaves some gaps for an AI agent.

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% (all parameters documented), so baseline is 3. The description adds meaning by explicitly stating the exclusive OR relationship between channelId and userId, which is not encoded in the schema. This improves parameter understanding.

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 clearly states the tool sends a message to a channel or user (DM). It uses a specific verb ('Send') and resource ('message'), and distinguishes from sibling tools (which are about reading messages, getting DMs, etc.).

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?

The description only mentions that one must specify either channelId or userId, but provides no guidance on when to use this tool versus alternatives like discord_get_messages or discord_resolve_dm_user. No exclusions or context are given.

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