Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

run_slash_command

Executes a Discord bot slash command in a channel or DM, including subcommands and named options, and returns the bot's reply or any modal to fill.

Instructions

Run a bot's slash command in a channel/DM, like typing /command. command can include subcommands ("music play"). options are by name. Returns the bot's reply (or a modal to fill).

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>",
      "command": "<command>"
    },
    "name": "run_slash_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoFiles to attach (each: path, url or data_base64)
commandYesCommand name, with subcommand group/subcommand separated by spaces, e.g. "imagine" or "config set"
optionsNoOption values by name, e.g. {"prompt": "a cat"}; users/channels/roles by ID; attachments by file index
channel_idYes
wait_secondsNoHow long to wait for the reply (default 15, 0 = don't wait)
application_idNoWhich app, if several have this command

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing the return shapes: the bot's reply, or a modal the caller must fill in — a non-obvious, agent-relevant outcome given readOnlyHint=false and openWorldHint=true. The wait_seconds semantics (default 15, 0 = don't wait) are also surfaced. It stops short of saying what happens on timeout or how a modal is subsequently submitted.

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?

A single dense sentence with the core action front-loaded and no filler. The parenthetical return-value clause is slightly compressed, but every clause carries information an agent needs.

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 six-parameter tool with nested option/file objects and no output schema, the description covers the essentials: what gets executed, how command and options are shaped, and what comes back. The remaining gap is failure/timeout behavior and how a returned modal is acted on, which an agent would likely need.

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 83%, so the schema already documents command, options, files, wait_seconds and application_id. The description only reinforces that options are keyed by name and that command encodes subcommands with spaces, which duplicates rather than extends the schema text. Baseline 3 is appropriate.

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 and resource ('Run a bot's slash command in a channel/DM') and grounds it with a concrete analogy ('like typing /command'). The sibling 'run_context_command' is not named or distinguished, so the agent cannot tell from this text alone which of the two entry points to use.

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 implied well through the '/command' analogy and the note that subcommands are space-separated, so an agent knows roughly how to invoke it. However, there is no explicit when-to-use/when-not, and no guidance on choosing this versus run_context_command or any create/modify command tool.

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