Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_server_deaf

Server deafen or undeafen a Discord voice member by guild and user ID, with an optional audit reason.

Instructions

Server deafen or undeafen a member in voice. Requires Deafen Members.

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": {
      "guildId": "<guildId>",
      "userId": "<userId>",
      "deaf": "<deaf>"
    },
    "name": "discord_set_server_deaf"
  }
}

Input Schema

NameRequiredDescriptionDefault
deafYes
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the required permission, which is the key operational constraint. It does not say the change is logged to the audit log, whether the action is reversible, how the boolean toggles state, or what a successful response contains.

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?

Two short sentences, action first and constraint second, with no filler. 'Server deafen or undeafen' is slightly awkward phrasing but the information density is good.

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 four-parameter mutation tool with no annotations and no output schema, the definition covers the action and the permission gate but leaves the boolean semantics, the reason field, and return behavior unaddressed. It is adequate to attempt a call but not to predict its effects.

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

Parameters2/5

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

Schema description coverage is only 25% (only guildId is documented), so the description needs to compensate and largely does not. It implies deaf=true means deafen and false means undeafen, but the 'reason' parameter (max 512 chars, presumably an audit-log reason) and the userId parameter are left unexplained in both places.

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 pair ('Server deafen or undeafen') and resource ('a member in voice'), which cleanly separates it from the mute-oriented sibling discord_set_server_mute. It is clear what the call does, though the scope is limited to the voice channel context stated in one phrase.

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 description names the prerequisite permission ('Requires Deafen Members'), which is genuine usage guidance, but it never explains when to prefer deafen over mute (discord_set_server_mute) or under what circumstances an agent should undeafen. Alternatives are only implied by the sibling list, not by the text.

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