discord-mcp

Server deafen / undeafen

server_deafen

Toggle a member's server deafen status in a voice channel. Use deafen=true to mute, deafen=false to restore audio.

Instructions

Toggle server-level deafen for a member in a voice channel. Pass deafen=false to undeafen.

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": {
      "member": "<member>",
      "deafen": "<deafen>"
    },
    "name": "server_deafen"
  }
}

Input Schema

Name	Required	Description
`deafen`	Yes	true to deafen, false to undeafen.
`member`	Yes	Member to deafen/undeafen (id, @mention, or username).
`server`	No	Server (guild) name or id. Optional when the bot is in a single server or DISCORD_GUILD_ID is set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only states the toggle action but does not disclose required permissions, side effects (e.g., does it affect the member's ability to speak?), or whether it is reversible. Minimal behavioral context beyond the schema.

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?

Single sentence that is front-loaded with the action ('Toggle server-level deafen'). Concise with no extraneous words. However, could be slightly more structured with separate from/use cases.

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 simple boolean toggle with 100% schema coverage and no output schema, the description is adequate. It mentions the voice channel context, but lacks details on return value, error conditions, or member state requirements.

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 100%, so baseline is 3. The description adds no new information beyond the schema; it repeats 'pass deafen=false to undeafen' which is already in the schema description. No additional meaning for parameters.

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?

Description clearly states the tool toggles server-level deafen for a member in a voice channel. It specifies the action (toggle) and resource (member's deafen status). It distinguishes from siblings like server_mute through the use of 'deafen' vs 'mute'. However, it does not explicitly differentiate from similar operations like server_mute.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like server_mute. No mention of prerequisites (e.g., member must be in a voice channel) or when not to use it. The description only states basic functionality without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.