Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_disconnect_member

Disconnects a Discord member from voice using guild and user IDs, with an optional reason; requires Move Members permission.

Instructions

Disconnect a member from voice. Requires Move Members.

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

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the required permission ('Move Members'), which is genuinely useful. However, it omits key behavioral facts such as whether the member stays in the guild, whether an audit-log reason is recorded, and what the response looks like on success or failure.

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?

Two short sentences, front-loaded with the action followed by the prerequisite. There is no filler or redundancy.

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?

With three parameters, no annotations, no output schema, and low schema coverage, the description should explain the 'reason' parameter and the outcome of disconnecting. It covers only the action and a permission requirement, leaving an agent to guess the rest.

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%: only guildId carries a description ('Discord id (snowflake)'), which userId inherits via $ref, while the optional 'reason' parameter is undocumented in both schema and description. The description adds nothing about parameter meaning, so it does not compensate for the coverage gap.

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 ('Disconnect a member from voice'), which is clearly distinct from sibling operations like discord_kick_member, discord_ban_member, and discord_move_member. It is not a restatement of the tool name's vague intent, though it does not explicitly name those siblings.

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?

The definition supplies a prerequisite ('Requires Move Members') but gives no guidance on when to choose this over discord_kick_member or discord_move_member, and no explicit exclusions. Usage context is implied by the verb only.

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