discord-mcp

guild_modify_current_voice_state

Idempotent

Update the bot's voice state in a stage channel to request to speak or toggle suppression.

Instructions

Purpose: Update the bot's own voice state in a stage channel (request to speak, toggle suppress).

When to use:

Bot wants to raise its hand (request_to_speak_timestamp = now) or step down (suppress = true).

Returns: {ok, guild_id}. Discord returns 204 (no body).

Input Schema

TableJSON Schema

Name	Required	Description
`guild_id`	Yes	Guild containing the stage channel
`suppress`	No
`channel_id`	No	Stage channel the bot is currently in
`request_to_speak_timestamp`	No	ISO8601 timestamp; null clears, future requests to speak

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.28.0Sep 15, 2026
- removedInput schema / properties / request_to_speak_timestamp / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / request_to_speak_timestamp / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv0.22.0Aug 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnly=false, idempotent=true, destructive=false, so the description does not need to repeat those. It adds value by explaining the specific state changes (request_to_speak_timestamp / suppress) and the exact return shape, including Discord's 204 no-body behavior.

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?

Three short, focused sections with no filler. The purpose is front-loaded, the usage conditions are explicit, and the return behavior is stated in a single line.

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

Completeness5/5

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

For a simple voice-state modifier with an output schema and adequate annotations, the description covers the operation, when to use it, and the return value. Nothing critical is missing for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75%, so the schema handles most parameters. The description adds meaning beyond the schema by explaining that suppress=true means step down and that request_to_speak_timestamp=now raises the hand, which the schema alone does not convey for suppress.

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 states a specific verb and resource: update the bot's own voice state in a stage channel, with concrete actions like request to speak and toggle suppress. It clearly distinguishes itself from sibling guild_modify_user_voice_state by scoping to the bot's own state.

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

Usage Guidelines4/5

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

The 'When to use' section gives concrete triggering conditions: raise hand or step down. It does not explicitly list exclusions or name an alternative tool, but the conditions are clear enough for an agent to decide when this is the right call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server