Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_my_nickname

Change your own nickname in a Discord server; use an empty string to reset it.

Instructions

Change your own nickname in a server (empty resets).

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>",
      "nick": "<nick>"
    },
    "name": "set_my_nickname"
  }
}

Input Schema

NameRequiredDescriptionDefault
nickYes
guild_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so the safety profile is covered. The description adds genuinely new behavior: an empty value resets the nickname, which is non-obvious for a required string field. It omits permission prerequisites (e.g. needing Change Nickname), which is the main remaining gap.

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?

A single front-loaded sentence with the reset behavior in a compact parenthetical; nothing is wasted. It is perhaps slightly too terse for a two-required-parameter mutation tool, but no sentence is filler.

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 simple two-parameter mutation the description covers purpose and the reset edge case, and no output schema exists so return values need not be explained. It stops short on permission requirements and guild_id format, which matter for correct invocation.

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 description coverage is 0%, so the description must compensate. It does partially: 'in a server' maps to guild_id and '(empty resets)' clarifies the nick field's semantics. However it never states that guild_id is a server/guild identifier format (snowflake) or that it must be a guild the caller belongs to.

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?

Specific verb ('Change') plus resource ('your own nickname') plus a scope qualifier ('in a server'). The phrase 'your own' implicitly separates it from set_member_nickname and set_friend_nickname, though no sibling is named explicitly.

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 implied rather than spelled out: the agent can infer this is for self-nickname edits scoped to one guild, and the parenthetical documents the reset path. There is no explicit when-not guidance or routing to set_member_nickname for editing someone else.

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