Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

join_voice_channel

Connect to a Discord voice or stage channel, or start and join a DM/group call, with options to ring participants and set mute, deafen, or video state.

Instructions

Join a voice/stage channel, or start/join a DM call (pass the DM channel_id; ring=true rings them). Note: you appear connected but no audio is streamed.

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": {
      "channel_id": "<channel_id>"
    },
    "name": "join_voice_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
ringNoDM/group calls: ring the other people
self_deafNo
self_muteNo
channel_idYes
self_videoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true, so they do not explain the surprising side effect. The description adds a genuinely important caveat that the connection is cosmetic and no audio is streamed, plus that ring notifies other participants. It does not cover permission requirements or what happens if the user is already connected elsewhere.

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 compact sentences with the primary action front-loaded before the DM-call variant and the ring parameter. Every clause carries distinct information, including the non-obvious no-audio caveat, and nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation tool with no output schema, the definition conveys the action, the DM-call variant, the ringing behavior, and the key limitation that no audio is streamed. The remaining gap is the meaning of the three self_* flags, which an agent must infer.

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 only 20%, with a description on ring alone. The description compensates for channel_id (DM vs guild channel) and for ring (it rings the other people), but self_mute, self_deaf, and self_video remain undocumented in both places. That is partial compensation, not full 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?

It states a specific verb and resource (join a voice/stage channel) and adds a distinct mode (start/join a DM call) in the same sentence, so an agent knows exactly what action this performs and can set it apart from leave_voice_channel. It stops short of naming which sibling handles the adjacent cases such as moving other members.

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?

It gives useful conditional guidance inside the action explanation: pass the DM channel_id for a DM/group call, and set ring=true to ring participants. That is real context for choosing the right invocation, but there is no explicit when-not-to-use guidance and no reference to alternatives like move_member_to_voice for moving someone else.

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