Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by jslay88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Send direct message

send_dm

Send a direct message to a Discord user by their user ID. Provide the user ID and message content to deliver private communication.

Instructions

Send a direct message to a user by their user ID.

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

Input Schema

NameRequiredDescriptionDefault
userIdYesThe Discord user ID to DM
contentYesMessage text (max 2000 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action, with no mention of side effects, permissions, failure modes, or what happens if the user cannot be messaged. For a mutating operation, this is a significant gap.

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, concise sentence that immediately conveys the core functionality. No filler or redundant information is present.

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 description is sufficient for a simple two-parameter tool with full schema coverage, but it lacks contextual completeness around usage timing, error handling, or any operational nuances. It provides the minimum viable information.

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 include meaningful descriptions (userId, content with max length). The tool description adds 'by their user ID' which reinforces the purpose but does not add significant new meaning beyond the schema.

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 action ('Send a direct message') and the target ('a user by their user ID'). This uniquely identifies the tool's purpose and distinguishes it from sibling tools like 'send_message' which likely sends to a channel.

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?

The description implies usage when you need to DM a user based on their ID, but it does not provide explicit guidance on when to choose this over alternatives like 'send_message'. No exclusions or alternative recommendations are offered.

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