Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_member_nickname

Changes a Discord member's server nickname in a guild; pass an empty nickname to reset it. Use set_my_nickname to update your own nickname.

Instructions

Change a member's server nickname (empty resets). For yourself use set_my_nickname.

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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>",
      "nick": "<nick>"
    },
    "name": "set_member_nickname"
  }
}

Input Schema

NameRequiredDescriptionDefault
nickYes
reasonNoAudit log reason
user_idYes
guild_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so mutation and scope are already covered. The description adds the useful empty-string-resets behavior and nothing more; it does not mention permission requirements, the audit-log reason parameter's implications, or that this affects a single guild only.

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, front-loaded sentences with no waste; the reset rule and the self-targeting alternative are both stated compactly. Slightly terse for a four-parameter mutation tool but structurally clean.

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 25% schema coverage, no output schema and no permission or prerequisite statement, the definition leaves real gaps. An agent knows what to do with nick but not the required scope, whether the target must be in the guild, or what a failure looks like.

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 coverage is only 25%, with guild_id and user_id undocumented in the schema, but the description clarifies only the nick parameter's empty-value semantics. The reason parameter's audit-log purpose is carried by the schema, not the description. The description adds meaning for the most ambiguous parameter but does not compensate for the low coverage overall.

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 specific verb and resource: change a member's server nickname, with the notable clarification that an empty value resets it. It also distinguishes itself from the sibling set_my_nickname for self-targeting, though it does not differentiate from set_friend_nickname.

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?

Explicitly routes the agent to set_my_nickname when targeting yourself, which is a real when-to-use signal. It gives no guidance on when nickname changes are not permitted, what permissions are needed, or why to prefer this over modify_guild_member.

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