Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_email_settings

Updates Discord account email preferences by applying the provided settings object, enabling changes to email-related options through the API.

Instructions

Modify Email Settings. [PATCH /users/@me/email-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": {
      "settings": "<settings>"
    },
    "name": "modify_email_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYessettings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the mutation and safety profile is partly covered without the description. The description adds only the HTTP method and endpoint path, both of which restate the annotation signal rather than adding context such as whether settings are merged or replaced, whether unspecified fields are reset, or what rate limits or permissions apply.

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 terse fragments with zero padding and the action front-loaded. Nothing is wasted, though the endpoint-path bracket carries little value for an agent deciding how to call the tool.

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 a nested free-form object parameter and no output schema, the definition is thin. It never states what a valid settings payload looks like, whether the PATCH is partial or whole-object, or what the response returns, leaving the agent to guess at the shape of the one required argument.

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 100%, so the single "settings" parameter is technically documented. However, that documentation is only the literal string "settings" on a free-form object with additionalProperties, and the description does nothing to clarify which keys are accepted or how partial updates are treated. This is the baseline case where the schema nominally covers parameters but the semantics remain thin.

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?

Gives a specific verb and resource ("Modify Email Settings"), so the basic action is identifiable, but it does nothing to distinguish it from the sibling get_email_settings beyond the read/write verb, and never says what an "email setting" comprises. The bracketed PATCH path is developer metadata rather than user-facing purpose.

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 guidance, no mention of the get_email_settings counterpart, and no prerequisites such as required scopes or authentication context. The agent is left to infer that this is the write counterpart to the settings-read tool.

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