Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_set_nickname

Idempotent

Update or remove a member's server nickname by providing the user ID, guild ID, and a new name (or null to clear). Records an optional reason in the audit log.

Instructions

Set or clear a member's server nickname. Pass null (or the string 'null') to clear it. Requires the Manage Nicknames permission (or Change Nickname for the bot itself). The reason is recorded in the audit log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoOptional reason recorded in the server audit log.
user_idYesDiscord user ID (snowflake) of the member.
guild_idYesDiscord server (guild) ID (snowflake).
nicknameYesNew nickname (max 32 characters), or null to clear it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / nickname / anyOf
      Added value: +[
+  {
+    "maxLength": 32,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / nickname / type
      Removed value: -"string"
    • addedInput schema / properties / user_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed4 schema fields changedv1.6.0
    • addedInput schema / properties / guild_id / description
      Added value: +"Discord server (guild) ID (snowflake)."
    • changedInput schema / properties / nickname / description
      Previous value: -"New nickname, or null to clear."New value: +"New nickname (max 32 characters), or null to clear it."
    • addedInput schema / properties / reason / description
      Added value: +"Optional reason recorded in the server audit log."
    • addedInput schema / properties / user_id / description
      Added value: +"Discord user ID (snowflake) of the member."
  4. Addedv1.5.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description reveals the null/string-'null' clearing behavior, the audit-log side effect of the reason, and the permission requirements. These are exactly the kind of behavioral details an agent needs that are not visible in the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences contain the action, the edge behavior, the permission requirement, and the audit-log effect with no filler. Every sentence earns its place.

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

Completeness5/5

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

For a simple mutation tool, the description covers what the action does, how to clear, who may call it, and a key side effect. The schema supplies the parameter formats, so no critical information needed to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explicitly stating that null or the string 'null' clears the nickname, an edge case not clear from the schema alone, and confirms the audit-log role of the reason parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Set or clear a member's server nickname,' which precisely states the action and target. It also clarifies the clear behavior and distinguishes the tool from permission/role-related siblings such as discord_set_member_permission.

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?

The description gives clear operating context: it is the tool to use for nickname changes, and it states the permission prerequisites ('Manage Nicknames' or 'Change Nickname for the bot itself'). It does not explicitly name alternatives or when-not-to-use conditions, so it stops one step short of a 5.

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