Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_channel_command_index

Read-only

Lists the application commands available in a specified Discord channel or DM so you can identify which slash commands can be used there.

Instructions

All commands usable in a channel or DM. [GET /channels/{channel_id}/application-command-index]

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": "get_channel_command_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 fully supplied externally. The description adds nothing beyond the endpoint path — no note on what the returned index contains, whether it varies by user permissions, or whether it is cached/eventually consistent. For a lookup whose results depend on the invoking context, that is a meaningful omission.

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 compact fragments with the functional statement front-loaded and the endpoint reference as secondary context. Nothing is redundant, though the endpoint string is close to filler for an agent that already knows the tool name.

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?

The tool is simple (one required param, full schema coverage, clear annotations, no output schema), so the description is not required to explain return values. However, since no output schema exists, an agent gets no signal about the shape or scope of the command index returned, which is the main residual gap.

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 coverage is 100% and the single channel_id parameter already documents that text, voice, thread, forum, and DM channels are accepted. The description adds no additional meaning about the identifier format or channel-type nuances beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 states the resource precisely: all commands usable in a channel or DM, backed by the endpoint path GET /channels/{channel_id}/application-command-index. That scope distinguishes it from guild-scoped, app-scoped, or user-scoped command index siblings without naming them. The verb is only implicit ('All commands usable...' rather than 'list'), which keeps it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the scope statement: an agent infers this is the tool for channel/DM command availability. The description never says when to prefer it over the sibling index tools (get_guild_command_index, get_app_command_index, get_user_command_index) or what prerequisites exist. It is adequate but leaves routing decisions to inference.

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