Skip to main content
Glama
Sign In
Discord MCP

Discord MCP

by RestartFU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_dm

Open a direct-message channel with a specified user ID, subject to Discord permissions.

Instructions

Open a direct-message channel with a user, subject to Discord permissions.

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": {
      "recipient_id": "<recipient_id>"
    },
    "name": "create_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipient_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

The description says 'subject to Discord permissions,' which hints at authorization requirements, but it does not explain side effects such as creating a new DM channel if one does not exist, nor does it mention rate limits or failure conditions. The openWorldHint suggests side effects, but the description leaves those details vague.

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. It conveys the core action, target, and a relevant constraint without any unnecessary words or repetition.

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 adequate for a simple tool, but it omits important context such as what the tool returns, whether an existing DM channel is reused, and any permission-related failure modes. Given no output schema is provided, a bit more detail would make it complete.

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

Parameters2/5

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

The schema provides only a parameter name and pattern, with no description. The tool description says 'with a user' but does not explicitly state that recipient_id is the user's ID or how it should be formatted. The parameter is somewhat self-explanatory, but the description does not fully compensate for the missing schema description.

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: opening a direct-message channel with a user. The phrase 'with a user' distinguishes this from general channel creation tools like create_channel, making the purpose unambiguous.

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 gives no explicit guidance about when to use this tool versus alternatives. Although 'direct-message' implies the intended use case, it does not mention when not to use it or contrast it with similar tools such as create_channel or send_message.

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