Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_create_group_dm

Initiate a group direct message by providing a list of user IDs. This tool gathers specified users into a new group conversation.

Instructions

Create a group DM with the given user IDs.

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": {
      "userIds": "<userIds>"
    },
    "name": "discord_create_group_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description only states the action 'Create' without disclosing side effects, permission requirements, rate limits, or potential failure modes. It is minimally informative.

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 with no redundant information. It is well-structured and efficient.

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

Completeness2/5

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

The description lacks details about return values, whether the tool requires authentication, or any context about group DM creation limits. It is insufficient for a tool with no output schema and no annotations.

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 description mentions 'user IDs' but does not clarify the format (Discord user IDs, usernames?) or constraints like minItems (2) found in the schema. It adds little beyond the parameter name.

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 verb 'Create', the resource 'group DM', and the method 'with the given user IDs', making the purpose unambiguous and distinguishing it from similar tools like discord_open_dm.

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 guidance is provided on when to use this tool versus alternatives like discord_open_dm or discord_send_message in an existing DM. There is no mention of prerequisites or limitations.

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