Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

mute_channel

Mute a Discord channel or DM to stop incoming messages and notifications, optionally for a set number of minutes.

Instructions

Mute a channel or DM (optionally for N minutes).

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": {
      "channel_id": "<channel_id>"
    },
    "name": "mute_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesNo
channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 and the bar is lower. The parenthetical '(optionally for N minutes)' usefully discloses that mutes can be temporary and therefore expire, but the description omits permission requirements and what mute actually suppresses.

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?

A single front-loaded sentence with the resource first and the optional modifier confined to a parenthetical; no filler. It is arguably over-compressed given the ambiguity it leaves, but nothing is wasted.

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 mutation tool with two parameters, 0% schema coverage and no output schema, the description is too thin: it leaves the mute semantics, ID format, and result behavior (e.g., confirmation, expiry field) entirely undocumented.

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 carry both parameters. It clarifies that 'minutes' is optional and accepts an arbitrary duration, but adds nothing about 'channel_id' — not its expected ID format (snowflake vs DM channel ID) nor whether a DM recipient ID differs from a channel ID.

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 and resource ('Mute a channel or DM') plus a scope qualifier that implicitly separates it from server-level muting siblings like mute_server. Clear enough to select without opening the schema, though no sibling is named explicitly.

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?

Provides no when-to-use, when-not, or alternative-selection guidance. It never says whether this mutes notifications for the calling user versus suppressing the channel for everyone, nor how it relates to mute_server or set_voice_mute.

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