Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_server_notifications

Choose which messages notify you in a Discord server—all, mentions only, or nothing—and optionally suppress @everyone and role pings.

Instructions

Choose which messages notify you in a server: all, mentions or nothing; optionally suppress @everyone / role pings.

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

Input Schema

NameRequiredDescriptionDefault
levelYes
guild_idYes
suppress_rolesNo
suppress_everyoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare this is a mutation (readOnlyHint=false) with openWorldHint=true, so the safety profile is partly covered. The description adds only the vague notion that the setting is per-user ('notify you'); it says nothing about permission requirements, whether it is a server-wide default versus per-channel override, or what happens to existing settings.

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 that leads with the core choice and appends the optional suppressions. Dense but free of filler; the semicolon-packed phrasing is slightly harder to parse than bullet-style framing would be.

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?

With four parameters and no output schema, the description covers the setting semantics adequately but leaves gaps: whether the setting is a server-level default, what the response or error looks like, and the role of the required guild_id identifier are unaddressed.

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 coverage is 0%, so the description must carry the load. It does explain the three level values and maps 'suppress @everyone / role pings' onto suppress_everyone and suppress_roles, but guild_id is left entirely unexplained and the enum values are already self-documenting in 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 names a concrete resource and action ('Choose which messages notify you in a server') and enumerates the exact option set (all, mentions, nothing), which maps directly onto the level enum. It is clear what the tool does, though it does not differentiate itself from nearby settings tools such as mute_server or set_channel_permission.

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?

Usage is implied by 'in a server' and 'notify you', giving a general sense of when to reach for it. There is no explicit when-not guidance and no named alternative for channel-level or temporary muting, so an agent must infer the boundary with mute_server.

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