Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_user_settings

Read-only

Retrieves your Discord account settings, including status, theme, locale, guild folders, and privacy options, so an assistant can review current preferences before changing them.

Instructions

Your client settings (status, theme, locale, guild folders, privacy…). [GET /users/@me/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_user_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds useful scope context by listing the kinds of settings included, but says nothing about authentication requirements, return shape, or whether values are defaults or overrides.

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?

It is a single front-loaded sentence plus an endpoint tag, with no filler. The bracketed REST path is developer-facing noise but small, and the trailing ellipsis in the field list weakens precision slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read with no output schema, the description gives enough to call it correctly: it identifies the target resource and sketches the returned content. The open-ended '…' means the agent cannot fully anticipate which settings keys come back, but annotations carry the rest of the burden.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The settings list in the description is the only semantic content and is consistent with the empty 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 (client settings / /users/@me/settings) and enumerates representative fields (status, theme, locale, guild folders, privacy), so an agent can tell this is a read of the current user's own settings. It is clear but does not explicitly differentiate itself from siblings such as get_email_settings or modify_user_settings beyond the field examples.

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 only implied: 'Your client settings' suggests reading the caller's own configuration, and the endpoint confirms it is scoped to @me rather than arbitrary users. There is no explicit statement of when to use this versus get_email_settings or modify_user_settings, and no exclusions are given.

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