Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_group_dm

Create a group DM with up to nine other Discord users by supplying their user IDs, with an optional name for the conversation.

Instructions

Create a group DM with friends (up to 9 others).

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": {
      "user_ids": "<user_ids>"
    },
    "name": "create_group_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
user_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so safety framing is covered. The description adds the meaningful 'up to 9 others' constraint, but does not say whether this creates a new channel or reuses an existing one, what permissions or friend relationships are required, or what happens on duplicate membership.

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?

A single short sentence with the constraint front-loaded and no filler. Nothing in it is redundant.

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?

For a mutation with no output schema and zero schema description coverage, the description leaves the 'name' parameter entirely undocumented and says nothing about return value or side effects. The 9-participant limit is the only substantive detail provided.

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?

Schema description coverage is 0%, so the description must carry parameter meaning and largely fails: 'with friends' loosely maps to user_ids but gives no format, ID type, or ordering, and the 'name' parameter is never mentioned at all. Only the 9-user cap adds real value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a group DM') and adds the concrete cap of 'up to 9 others', which distinguishes it from a plain 1:1 DM tool like open_dm. It does not explicitly name or contrast with sibling tools, so it stops short of a 5.

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 on when to prefer this over open_dm or send_dm, no prerequisites such as sharing a server/friendship with the listed users, and no note about what happens if a group with the same members already exists. The only implicit cue is 'group' implying multiple participants.

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