Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_notification_settings

Updates desktop and mobile notification flags for the current Discord account by patching notification settings.

Instructions

Desktop/mobile notification flags. [PATCH /users/@me/notification-settings]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "modify_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 bar for additional disclosure is lower, but the description adds nothing beyond them. It does not say whether the flags payload is merged with or replaces existing settings, nor what happens if the flags field is omitted on a PATCH.

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 fragments, no filler, and the resource statement comes first. It is compact rather than bloated, though it is arguably too terse rather than too long.

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 single-parameter mutation tool with annotations covering the safety profile and no output schema, the minimum is met, but a bare numeric bitfield with no explanation of its bits leaves the agent unable to construct a correct call.

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% for the only parameter, and the description supplies no meaning at all for "flags" beyond repeating the word. A numeric bitfield is exactly the kind of parameter that needs bit meanings or a pointer to documentation, and none is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Desktop/mobile notification flags" names the resource and hints at which notification channel is affected, partially distinguishing it from modify_email_settings or modify_thread_settings siblings. However, it never states a verb (set/update/modify) and the only action signal is the bracketed endpoint PATCH /users/@me/notification-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?

There is no when-to-use guidance, no mention of prerequisites or auth scope, and no routing to alternatives such as modify_email_settings or modify_thread_settings. The agent must infer usage entirely from the tool name.

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