Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_dms

List your existing DM and group DM channels so you can identify which conversations your account is able to message.

Instructions

List existing DM and group DM channels. Only these channels can be messaged by the account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discord_list_dms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoMatch recipient username or channel name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely useful behavioral constraint (only these channels are messageable by the account), but it omits pagination behavior, whether results are scoped to the account's participations, and any rate-limit or permission context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the resource identification is front-loaded. The second sentence is slightly compressed in a way that requires interpretation, but nothing is wasted.

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?

For a small two-parameter list tool with no output schema and no annotations, the description covers purpose and one behavioral constraint but leaves result shape, default limit behavior, and DM-vs-group-DM differentiation unstated. Adequate to invoke, thin for interpreting results.

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 50%: 'query' is documented in the schema but 'limit' is not, and the description adds no meaning for either. It never explains that results are truncated at 50 by default or capped at 200, nor how 'query' matching interacts with group DM names.

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 gives a specific verb plus a specific resource ('List existing DM and group DM channels'), and the scoping to DM/group-DM channels distinguishes it from the general discord_list_channels sibling without naming it. An agent can tell what it returns, though the boundary with discord_list_channels is only implied.

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 second sentence ('Only these channels can be messaged by the account') implies the reason to call it — to discover valid message targets — but never states when to prefer this over a sibling or any prerequisite/exclusion. Usage must be inferred rather than read.

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