Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

server_deafen_member

Toggle server deafen status for a Discord member in voice using guild and user IDs, with an optional audit log reason.

Instructions

Server-deafen or undeafen a member in voice.

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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>",
      "deaf": "<deaf>"
    },
    "name": "server_deafen_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
deafYes
reasonNoAudit log reason
user_idYes
guild_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the description could have spent its words on what those flags don't cover: required permissions such as DEAFEN_MEMBERS, whether server-deafening also blocks the member from speaking/hearing, and what happens if the target is not in voice. None of that is present, so the description adds essentially nothing beyond the structured flags.

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?

One short sentence with the action and scope front-loaded and no filler. It is efficient, though its brevity is closer to under-specification than to disciplined economy for a 4-parameter mutation.

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

Completeness2/5

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

For a voice-state mutation with 25% schema coverage and no output schema, the description omits permissions required, failure conditions (target not in voice), and side effects on the member's audio state. An agent could call it, but not confidently predict whether the call will succeed or what it changes.

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 description coverage is only 25% (only 'reason' is documented), so the description carries real weight here. It does convey the key semantics of the 'deaf' boolean — true deafens, false undeafens — but leaves guild_id, user_id and the audit-log 'reason' behavior entirely to the schema and to name inference.

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?

The description names a specific verb pair (server-deafen / undeafen), the resource (a member) and the scope (in voice), so an agent can distinguish it from generic member modification tools. It does not explicitly contrast with the nearby server_mute_member sibling, but 'deafen' vs 'mute' is a clear enough distinction on its own.

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?

There is no when-to-use guidance: nothing says this applies only to members currently connected to a voice channel, nothing distinguishes deafen from server mute, and no prerequisites (bot permissions, membership) are stated. The agent must infer all conditions from the name.

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