Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

select_menu_option

Select one or more options in a select menu on a Discord bot message by providing option values or user, role, and channel IDs.

Instructions

Choose option(s) in a select menu on a bot message (values = option values, or user/role/channel IDs for those menus).

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": {
      "message": "<message>",
      "values": "<values>"
    },
    "name": "select_menu_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes
messageYes
custom_idNoWhich menu (default: the first)
channel_idNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this triggers an external interaction. The description adds the important semantic that values may be raw option values or user/role/channel IDs depending on menu type, but says nothing about side effects (the bot receives an interaction), permissions, or what wait_seconds controls.

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 the key value-format caveat in a parenthetical; no filler. It is compact to the point of omitting required parameter context, but nothing written is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter interaction tool with only 20% schema coverage, no output schema, and open-world side effects, the description is too thin: it never identifies what the message parameter must contain, what channel_id is for, or what wait_seconds governs, and gives no indication of what a successful selection returns.

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 20% – just custom_id is documented. The description usefully explains the semantics of values (option values vs. snowflake IDs by menu type), which is the highest-value parameter, but leaves message, channel_id and wait_seconds completely undefined in both schema and prose.

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 a specific verb and resource: choosing option(s) in a select menu attached to a bot message. It is immediately distinguishable from the sibling set (accept_*, add_*, bulk_*), none of which interact with message components, though it does not name or contrast any sibling 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 is implied – this is the tool for interacting with select menus on bot messages – but there is no explicit when-to-use statement, no preconditions (e.g. that the message must still have a live component), and no guidance on choosing among options like multi-select or when to pass channel_id.

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