Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_voice_mute

Mute, deafen, or turn off your camera in the voice channel you are in by setting self-mute, self-deafen, and video flags for a server or DM call.

Instructions

Mute/deafen/camera yourself in the voice channel you are in.

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": "set_voice_mute"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idNoServer (omit for DM calls)
self_deafNo
self_muteNo
self_videoNo

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?

Annotations already declare this is a non-destructive, non-read-only, open-world mutation, so the safety profile is largely covered. The description contributes the self-only scoping and the connected-to-voice precondition, but omits key behavior: whether unspecified booleans are left untouched or reset, whether calls are idempotent, and what the result looks like on failure.

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?

A single front-loaded sentence with no filler; the action and the scope arrive immediately. The compressed phrasing "Mute/deafen/camera yourself" is slightly awkward since "camera" is not a verb, but it costs almost no reading effort.

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?

No output schema exists, so the description would ideally mention the return shape, and with 25% schema coverage and an overlapping sibling, more detail on flag semantics and alternatives would help. Still, for a zero-required-parameter self-toggle tool with annotations carrying the destructive profile, the description covers the essential precondition and effect mapping.

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?

Only guild_id has schema documentation (25% coverage), but the description partially compensates by mapping the three boolean parameters to their effects: mute, deafen and camera. The critical semantics of those booleans are still missing: nothing says whether an omitted flag is unchanged or set to false, and the camera flag is ambiguously stated as an action rather than a boolean target.

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?

"Mute/deafen/camera yourself in the voice channel you are in" states a concrete action set and explicitly scopes it to the caller's own voice state, which separates it from mute_channel, mute_server and server_mute_member that act on other targets. It stops short of naming the overlapping sibling modify_current_user_voice_state, so the boundary is inferable rather than stated.

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 phrase "in the voice channel you are in" implies the precondition of being connected to voice, which is useful context for when the call is valid. However, there is no explicit when-to-use guidance, no statement of what happens if the user is not in a channel, and no differentiation from modify_current_user_voice_state, which appears to cover the same territory.

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