Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

mute_server

Mutes a Discord server's notifications, optionally for a set number of minutes, to silence alerts without leaving the server.

Instructions

Mute a server's notifications (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": {
      "guild_id": "<guild_id>"
    },
    "name": "mute_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesNo
guild_idYes

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?

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds that the mute can be time-bounded, but does not say whether omitting the duration mutes indefinitely, whether privileges are required, or whether the setting is per-user. That leaves meaningful behavioral gaps for a state-changing call.

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 short sentence with the action front-loaded and the optional duration parenthetically attached; nothing is wasted, though the terseness arguably costs clarity on defaults.

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 two-parameter mutation with no output schema, the definition covers the core action but omits the default duration semantics and permission expectations. It is minimally adequate rather than complete.

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

Parameters3/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 parameter meaning. It does explain that `minutes` is optional and is a duration in minutes, but it never states the default/indefinite behavior when omitted, and `guild_id` is left entirely to the schema.

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 states a specific verb and resource: 'Mute a server's notifications', which is clearly distinct from channel-level or member-level muting siblings. It stops short of naming any sibling explicitly, so sibling differentiation relies on the 'server's notifications' qualifier alone.

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 reference to unmute_server, set_server_notifications, or mute_channel as alternatives. The agent must infer from the name which of the many mute-related siblings applies.

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