Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_move_member

Moves a Discord member to a specified voice channel, or disconnects them when channelId is null, for server moderation and voice channel management.

Instructions

Move a member to another voice channel, or disconnect them with channelId null. 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>",
      "channelId": "<channelId>"
    },
    "name": "discord_move_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)
channelIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 'Move Members' permission and what channelId null does, which is valuable. It omits whether the target must currently be in a voice channel, what happens on failure, and that the call is a mutation affecting another user.

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 with zero waste; the primary action is front-loaded and the special case follows immediately.

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 4-parameter mutation tool with no annotations and no output schema, the definition covers the core action and permission but leaves the audit 'reason' parameter, failure conditions, and response shape unaddressed. Adequate but visibly incomplete.

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 50%, and the description adds real meaning for channelId by defining the null sentinel as 'disconnect'. However the 'reason' parameter and the userId requirement are never mentioned, leaving half the surface to the schema alone.

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?

States a specific verb and resource ('Move a member to another voice channel') and clarifies the null-channel edge case as a disconnect. It is less clear against the sibling discord_disconnect_member, which this description effectively duplicates via 'channelId null', so it does not fully differentiate itself from alternatives.

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 description implies two usage modes (move vs disconnect-via-null) but never says when an agent should pick this over discord_disconnect_member, which appears to do the same thing. No prerequisites or exclusions beyond the permission note.

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