Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_server_mute

Mutes or unmutes a member in Discord server voice channels, enabling voice moderation with Mute Members permission.

Instructions

Server mute or unmute a member in voice. Requires Mute 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>",
      "mute": "<mute>"
    },
    "name": "discord_set_server_mute"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteYes
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the required permission ('Mute Members') and that the operation is a reversible toggle via the mute flag, but it does not say that muting applies across all voice channels, whether the target must currently be connected, or how the change can be undone if invoked in error.

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 with the action front-loaded and the permission requirement second, with no filler. It is efficient, though the extreme terseness leaves the gaps noted in other dimensions rather than spending words where they would help.

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 four-parameter mutation tool with no annotations, no output schema, and thin schema descriptions, the definition is under-specified: reason semantics, toggle direction, and the effect/scope of a server mute are all left to outside knowledge. The permission note is the only behavioral content beyond the name.

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% (just guildId is documented as a snowflake), so the description needs to compensate and largely does not. It never explains that mute=true mutes and mute=false unmutes, and the 512-character reason parameter and its audit-log purpose are entirely undocumented in both schema and description.

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 (mute/unmute) and a specific resource (a member's voice state on a server), which is distinguishable from the closest sibling discord_set_server_deaf. It stops short of explicitly naming that sibling as the alternative, so it is clear but not maximally differentiated.

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 'Requires Mute Members' clause gives a concrete precondition for invocation, which is real guidance. However, there is no statement about when to prefer this over adjacent actions such as server-deafen or disconnecting a member, so the when-not guidance is only implied.

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