Disconnect a member from their current voice channel by specifying their user ID, with optional reason and server. Useful for moderation or managing voice sessions.
Disconnect a member from their current voice channel
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Audit log reason | |
| userId | Yes | Target User ID | |
| guildId | No | Discord server ID (defaults to DISCORD_GUILD_ID) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a voice-state mutation but does not disclose permissions required, side effects, reversibility, or what happens if the user is not in a voice channel.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with zero wasted words. It immediately identifies the action and target resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description is too thin. It omits prerequisites, alternatives, permission requirements, and behavioral details an agent needs to invoke it safely and correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so userId, guildId, and reason are already documented in the schema. The description does not add any parameter-specific meaning beyond what the structured fields provide, making 3 the appropriate baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: disconnect a member from their current voice channel. It is distinguishable from move_voice_member and modify_voice_state in intent, but it does not explicitly name alternatives or clarify sibling boundaries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus move_voice_member, modify_voice_state, or kick_member. The description only says what the tool does, leaving all usage context implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.