Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

run_context_command

Executes a Discord Apps context-menu command on a user or message by providing channel ID, command name, and target ID.

Instructions

Run an "Apps" right-click command on a user or a message (context-menu command).

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>",
      "target_id": "<target_id>"
    },
    "name": "run_context_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesCommand name as shown in the Apps menu
target_idYesUser ID (user command) or message ID (message command)
channel_idYes
wait_secondsNo
application_idNo

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?

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is carried structurally. The description adds that this dispatches a third-party 'Apps' context-menu command, which is meaningful context, but it omits what the invocation returns, whether side effects occur in the target channel, and any rate-limit or permission constraints on executing another app's command.

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 front-loaded sentence with no padding; the parenthetical is mildly redundant with 'right-click command' but not wasteful.

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 5-parameter, open-world invocation with no output schema, the definition covers the core action but leaves significant gaps: the semantics of wait_seconds, why application_id may be required, and what happens on an unregistered or ambiguous command name. Adequate to start, insufficient for confident invocation in edge cases.

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 coverage is only 40%: command and target_id are documented in the schema, and the description's 'user or a message' largely restates the target_id description rather than extending it. Nothing in the description explains channel_id, wait_seconds, or application_id, which are undocumented in both places — the description does not 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 and resource ('Run an "Apps" right-click command') and pins the target domain ('on a user or a message'). The parenthetical 'context-menu command' implicitly separates it from the slash-command sibling, but 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?

Usage context is implied by 'right-click command on a user or a message', so an agent can infer this is for context-menu interactions rather than slash commands. However, there is no explicit when-to-use/when-not guidance, no mention of run_slash_command as the alternative, and no prerequisite that the command must already be registered by an application.

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