Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_email_settings

Read-only

Retrieve the authenticated Discord account's email notification and communication settings. Use it to inspect current email preferences before updating account notifications.

Instructions

Get Email Settings. [GET /users/@me/email-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": "get_email_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds only an HTTP path fragment and discloses nothing about what the settings contain, whether authentication/scopes are required, or how the response is shaped, despite there being no output schema to fall back on.

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?

Extremely short and front-loaded, with the resource named first and the endpoint as a bracketed suffix. Nothing is wasted, though the same brevity is what leaves the other dimensions thin.

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 no parameters and no output schema, the description is arguably enough to invoke the tool, but it leaves a real gap: nothing describes the returned settings object that the agent will have to interpret. Annotations cover the safety profile, so this is minimally adequate rather than insufficient.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty object, so there is no parameter semantics to explain. The baseline of 4 applies; the description neither helps nor misleads in this dimension.

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 description gives a verb+resource ('Get Email Settings') plus the underlying endpoint path, which does distinguish it by name from the sibling modifier 'modify_email_settings'. However, 'Get Email Settings' largely restates the tool name, and it never says what these settings actually are, so an agent learns nothing beyond the obvious read-vs-modify split.

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?

No when-to-use guidance is offered: nothing says whether this is per-user, per-account, or when an agent should call it instead of get_user_settings or /users/@me related reads. The read-only verb implies a retrieval context, but the definition states no exclusions or conditions.

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