Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

server_mute_member

Mute or unmute a Discord server member in voice channels by specifying the guild, user, and mute state, with an optional audit log reason.

Instructions

Server-mute or unmute 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>",
      "mute": "<mute>"
    },
    "name": "server_mute_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteYestrue = mute, false = unmute
reasonNoAudit log reason
user_idYes
guild_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully clarifies that the mute applies to voice rather than text, but says nothing about required permissions (e.g., Mute Members), audit-log behavior from the reason field, or that the effect persists until unmuted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, which is good. However, it is under-specified rather than concise; the brevity removes information an agent needs rather than removing waste.

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 4-parameter mutation tool with no output schema and only hint-level annotations, the description is thin. It omits permissions, reversibility/persistence, audit-log semantics of reason, and any hint about the response, leaving the agent to infer mutation behavior from the name alone.

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 50%: mute and reason are documented in the schema, but guild_id and user_id have no description anywhere. The description does not compensate—it never mentions targets or identifiers—so half the parameters carry no meaning into the call.

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 concrete verb pair (server-mute/unmute), the resource (member), and the scope (in voice), which is more specific than a bare 'mute' tool. It stops short of distinguishing itself from siblings like mute_server, set_voice_mute, or mute_channel, so the agent must infer the difference from names.

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 or when-not-to-use guidance and no named alternative. The 'in voice' phrase implies a voice-channel context, but the agent is left to guess how this differs from other mute-flavored siblings.

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