Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

leave_voice_channel

Disconnect from a Discord voice channel or DM call. Provide a guild ID for server voice; omit it to leave a direct-message call.

Instructions

Disconnect from voice (in a server: pass guild_id; omit for DM calls).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "leave_voice_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the agent knows this is a non-destructive state change against an open-world service. The description adds the server-vs-DM mode split, but says nothing about behavior when not connected, whether the disconnect is idempotent, or whether it affects other participants.

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?

One sentence plus a parenthetical, with the action front-loaded and the conditional mode detail immediately after. No filler and nothing redundant.

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 one-optional-parameter tool with no output schema and annotations covering the safety profile, the description supplies the key disambiguation an agent needs. It only omits edge-case behavior (error when not in voice), which is minor at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single property is a bare 'guild_id' string, so the description carries the full burden. It does so well: it explains that supplying guild_id targets a server call and omitting it targets a DM call, which is exactly the meaning missing from the schema.

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: 'Disconnect from voice.' The parenthetical scopes it to self-disconnection in a server vs DM, which distinguishes it from a generic channel-leave operation, though it does not explicitly name the sibling it complements (join_voice_channel) or the moderator variant (disconnect_member_from_voice).

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 parenthetical gives a practical condition: pass guild_id in a server, omit it for DM calls. That is conditional guidance for invocation, but there is no statement of when to use this tool rather than a sibling, nor any exclusion or prerequisite (e.g., must currently be connected).

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