Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

open_dm

Opens or retrieves a direct message channel with a specified Discord user and returns its channel ID, so you can start or continue a private conversation.

Instructions

Open (or get) the DM channel with a user; returns its channel 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": {
      "user_id": "<user_id>"
    },
    "name": "open_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and readOnlyHint=false, so the risky part is creation, and "Open (or get)" usefully signals get-or-create idempotent behaviour plus the return value. However, nothing is said about permissions, whether opening triggers notifications/visibility to the other user, or rate limits — meaningful gaps for a mutating tool.

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?

One compact sentence that front-loads the operation and appends the return value; every clause earns its place with no filler.

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

Completeness4/5

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

For a single-parameter tool with no output schema, the description covers the operation, the get-or-create nuance, and the return value, which is close to sufficient. It falls short only on failure modes and permission requirements.

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 0% for the single required parameter, but the name user_id is self-describing and "with a user" maps directly onto it. The description adds no format detail (e.g. snowflake ID as string) beyond that implicit mapping.

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?

The description uses a specific verb+resource ("Open (or get) the DM channel with a user") and even states the return value (channel ID). It is clear about the operation, though it does not explicitly distinguish itself from sibling get_dm_channel or create_group_dm.

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 parenthetical "(or get)" implies a get-or-create usage pattern, which is useful, but there is no explicit statement of when to prefer this over get_dm_channel or create_group_dm, nor any prerequisites. Usage is implied rather than directed.

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