Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

disconnect_member_from_voice

Destructive

Disconnects a Discord member from their voice channel using guild and user IDs, with an optional audit log reason.

Instructions

Disconnect a member from voice.

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>"
    },
    "name": "disconnect_member_from_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason
user_idYes
guild_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is known from structured data. The description adds nothing beyond that — it doesn't say whether the member can immediately rejoin, what permissions are required, or how this differs from kicking a member from the guild.

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?

The single sentence is front-loaded and free of padding, which is structurally clean. It is arguably too terse to be genuinely helpful, but it contains no wasted wording.

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 destructive, open-world mutation tool with no output schema and two undocumented parameters, the description should explain permissions, side effects, and the audit-log reason's role. Given the crowded sibling space around member and voice operations, the current text is insufficient to call the tool confidently.

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 33%: guild_id and user_id have no schema descriptions, and the description supplies no meaning for them either. Only the optional 'reason' parameter is documented ('Audit log reason'), so the description fails to compensate for the low coverage.

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 — disconnecting a member from voice — which is distinct from siblings like move_member_to_voice or kick_member. It is clear what the tool does, though it doesn't explicitly contrast itself with those alternatives.

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?

There is no when-to-use guidance, no prerequisites (permissions, member must be connected to voice), and no mention of alternatives such as kick_member or move_member_to_voice. The agent must infer all selection logic from the name alone.

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