Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_request_to_speak

Raise your hand to speak in Discord Stage channels, or lower it by setting cancel to true.

Instructions

Raise your hand to speak in a Stage (set cancel:true to lower).

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": {
      "guildId": "<guildId>",
      "channelId": "<channelId>"
    },
    "name": "discord_request_to_speak"
  }
}

Input Schema

NameRequiredDescriptionDefault
cancelNo
guildIdYes
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It states the basic action and the effect of the 'cancel' parameter, but does not mention permissions, side effects, or what happens after the request (e.g., approval process). Minimal but not misleading.

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 that immediately communicates purpose and syntax. No wasted words.

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?

Given no output schema and no annotations, the description is too brief. It does not mention that the user must be in a Stage channel, any permissions needed, or the outcome of the request. Partially complete for a simple action but leaves gaps.

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 description coverage is 0%, so the description must compensate. It explains the 'cancel' parameter ('set cancel:true to lower'), but does not explain 'guildId' or 'channelId', which are common Discord IDs. The description adds some value but insufficient for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: 'Raise your hand to speak in a Stage' and explains the inverse action using 'cancel:true to lower'. It uses a specific verb and resource, and distinguishes from siblings like 'discord_set_voice_state'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., 'discord_set_voice_state' or 'discord_modify_user_voice_state'). The description lacks context about prerequisites like being connected to a Stage channel.

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