Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_nickname

Set or clear a Discord member's nickname by passing null; requires Manage Nicknames permission.

Instructions

Change a member nickname, or clear it with null. Requires Manage Nicknames.

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": {
      "guildId": "<guildId>",
      "userId": "<userId>",
      "nickname": "<nickname>"
    },
    "name": "discord_set_nickname"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)
nicknameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden; it does disclose the permission gate and the destructive-ish null semantics, which are the two most important facts. It does not say what the change affects (guild-scoped only?), whether it is reversible, or what happens on insufficient permissions/errors.

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 and the clear-with-null detail; no filler. The permission note could arguably be folded in more tightly but nothing is wasted.

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-field mutation on a guild member, the essentials (target field, null to clear, permission requirement) are covered. Missing are the reason/audit-log parameter's purpose and basic failure behavior, which matter for a permission-gated write tool with no annotations.

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 coverage is only 25% — just guildId is described as a snowflake — so the description must compensate. It usefully explains that nickname may be null to clear, but says nothing about userId or the reason parameter (which is clearly audit-log text given its 512-char cap, yet undocumented).

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 concrete verb and resource ("Change a member nickname") plus the alternative outcome (clear it with null), which is more precise than the bare tool name. It does not explicitly differentiate itself from near-neighbors like discord_set_global_name, so the sibling boundary is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real prerequisite ("Requires Manage Nicknames") and the condition for the null case, which is genuine when-to-use context. It stops short of naming any alternative tool or when not to use it.

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