Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_user_voice_state

Invite a user to speak or move them to the audience in a Discord stage channel by updating their voice state.

Instructions

Invite a user to speak (suppress=false) or move them to the audience in a stage channel. [PATCH /guilds/{guild_id}/voice-states/{user_id}]

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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>",
      "channel_id": "<channel_id>"
    },
    "name": "modify_user_voice_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
user_idYesUser ID
guild_idYesServer (guild) ID
suppressNoSuppressed (audience) in a stage
channel_idYesChannel ID

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?

Annotations already declare non-read-only, non-destructive, open-world behavior, so the description's added value is the PATCH endpoint and the boolean-to-outcome semantics. It omits permission requirements (stage moderator / mute-members), behavior when the target is not in the channel, and any failure modes for this mutation.

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?

Two short sentences, front-loaded with the action and its two modes. The bracketed HTTP path is developer metadata rather than agent-facing guidance, a minor piece of noise in an otherwise tight definition.

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 five-parameter mutation with no output schema, the description covers the operating modes but leaves preconditions (target already in the stage channel, required permissions) and the meaning of channel_id unaddressed. Adequate to attempt a call, not complete enough to guarantee a correct one.

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 100%, so the schema already documents all five parameters, including 'suppress' as audience suppression in a stage. The description adds only a thin value in pairing suppress=false with speaking, while channel_id's role (must be the stage channel) and reason are left unelaborated.

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 concrete verb and resource ('modify user voice state') and narrows scope to stage channels, with the two outcomes named (invite to speak / move to audience). It does not explicitly distinguish itself from close siblings like modify_current_user_voice_state, so it stops short of a 5.

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 rather than stated: the stage-channel context and the suppress=false mapping tell the agent when this applies. There is no explicit exclusion or pointer to alternatives (e.g., set_voice_mute or modify_current_user_voice_state), leaving selection to inference.

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