better-discord-mcp

by Sys0xdbg

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

discord_set_voice_state

Mute or deafen a member in a Discord voice channel by providing the guild and user IDs.

Instructions

Server mute/deafen a member (mute/deaf booleans).

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>"
    },
    "name": "discord_set_voice_state"
  }
}

Input Schema

Name	Required	Description	Default
`deaf`	No
`mute`	No
`reason`	No
`userId`	Yes
`guildId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description should fully disclose behavior. It only states the action (mute/deafen) but omits critical details: whether changes are persistent, if requires permissions, side effects on the user's client, or if it applies globally to the server. The description is insufficient for an AI agent to anticipate outcomes.

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

Conciseness2/5

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

The description is extremely concise (one short sentence), but this comes at the cost of omitting essential information. It is not efficiently structured to convey the tool's full purpose and parameters. A more informative but still concise description would be better.

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

Completeness1/5

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

Given 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain required parameters (guildId, userId), the effect of missing booleans, or what the tool returns. An AI agent would struggle to use this tool correctly without additional context.

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 0%, so the description must compensate. It mentions 'mute/deaf booleans' but does not explain the other 3 parameters (reason, userId, guildId) beyond their obvious names. An agent cannot determine formatting constraints or the need for userId/guildId values.

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 clearly states the tool's purpose: to server mute or deafen a member, using specific boolean parameters. It identifies the verb (mute/deafen) and resource (member), but does not explicitly distinguish it from siblings like 'modify_user_voice_state' or 'set_voice_status'.

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 guidelines are provided on when to use this tool versus alternatives, nor any prerequisites (e.g., user must be in a voice channel, required permissions). The description gives no usage context.

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

Deploy Server