Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_commands

Read-only

Discovers available slash and context-menu commands in a Discord channel or DM so you can identify commands from bots and installed apps, with optional filtering by command or app.

Instructions

List slash commands and context-menu commands you can use in a channel/DM (from all bots there and your user-installed apps).

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": {
      "channel_id": "<channel_id>"
    },
    "name": "list_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFilter by command or app name
channel_idYes
application_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context that results are aggregated from all bots in the channel plus user-installed apps, but says nothing about permission requirements, pagination, or result ordering.

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 front-loaded sentence with the resource named first and the scoping detail in parentheses. No filler, no redundancy.

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?

Adequate for a simple read-only list tool with three parameters and no output schema, since annotations cover the safety profile. However, with two of three parameters undocumented anywhere, the definition leaves an agent guessing about the required channel_id format and the purpose of application_id.

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 only 33%: query is documented in-schema, while the required channel_id and the optional application_id have no descriptions. The description implicitly motivates channel_id ("in a channel/DM") but gives no clue what application_id does, so it fails to compensate for the coverage gap.

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 (List) and resource (slash commands and context-menu commands usable in a channel/DM), plus the scope of sources (bots in that channel and user-installed apps). This differentiates it from the global/guild application-command listing siblings by scope, though it never names those alternatives 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?

Implies when to use it: when you want commands usable in a specific channel or DM, aggregated across bots and user-installed apps. It gives no explicit exclusions or routing to siblings such as list_global_application_commands or list_guild_application_commands when the agent actually wants a guild's registered commands rather than usable ones.

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