Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_dm_channel

Read-only

Retrieve the existing direct message channel with a Discord user by their user ID, so you can inspect or use that DM conversation.

Instructions

Get the existing DM channel with a user (if any). [GET /users/@me/dms/{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": {
      "user_id": "<user_id>"
    },
    "name": "get_dm_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID

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 readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds that the DM may not exist ('if any'), which is genuinely useful behavioral context, but it says nothing about the failure mode (empty result vs error) or the shape of the returned channel.

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?

Two short clauses with the core action front-loaded and the endpoint appended as a locating anchor. Every word earns its place; nothing is redundant.

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 one-parameter read tool with existing annotations and no output schema, the description is close to sufficient. The remaining gap is what is returned when a DM exists versus when it does not, which the description only gestures at with '(if any)'.

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?

The single user_id parameter has full schema description coverage, so the schema does the documentational work. The description's phrase 'with a user' confirms the parameter's role but adds no format, type, or sourcing detail beyond what the schema states.

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?

Names a specific verb and resource ('Get the existing DM channel with a user') and adds the REST endpoint for grounding. The '(if any)' qualifier signals this is a lookup of an existing DM rather than a creation, which helps distinguish it from creation-oriented siblings, though no sibling is named explicitly.

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 '(if any)' hints that this is the read-only path for an existing DM and that it may return nothing, which implies an alternative creation path exists. However, it never states when to use this versus open_dm or create_group_dm, nor what to do when no DM exists.

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