Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_thread_settings

Change notification preferences for a Discord thread by setting mute status, mute configuration, or flags to receive all messages, mentions only, or no notifications.

Instructions

Change your notification settings for a thread. [PATCH /channels/{channel_id}/thread-members/@me/settings]

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": "modify_thread_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoThread member flags (notifications: 2 all, 4 mentions only, 8 nothing)
mutedNomuted
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
mute_configNo

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 readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is largely covered. The description adds one useful behavior beyond that: the @me path segment signals the change applies only to the calling user's thread membership, not other members'. It says nothing about whether omitted fields are preserved, whether mute_config can be cleared, or rate limits.

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?

Two short sentences, front-loaded with the action, with the HTTP endpoint appended as a compact technical anchor. Nothing is redundant, though the endpoint adds little for an agent that already has the schema.

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 mutation tool with a 4-parameter schema, no output schema, and annotations covering safety, the description is adequate but thin. It omits whether the call replaces or merges settings, how to reset a mute, and what a successful response confirms — gaps an agent would want before invoking it.

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 75%, so the schema already documents channel_id, muted, flags (with the 2/4/8 bit meanings), and mute_config. The description adds no parameter-level meaning such as the interaction between muted and flags or how to un-mute. Baseline 3 is appropriate when the schema carries the parameter burden.

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: 'Change your notification settings for a thread.' The 'your' plus the PATCH path @me makes clear it mutates only the caller's own thread membership settings, which is a meaningful distinction. It does not, however, explicitly differentiate itself from sibling settings tools like modify_notification_settings or modify_user_guild_settings.

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?

The description gives no when-to-use guidance, no prerequisites, and no mention of alternatives such as global versus per-guild notification settings. An agent must infer from the name alone that this is the per-thread override rather than the account-wide setting.

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