Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_current_guild_member

Update your own nickname, avatar, banner, bio, or pronouns in a Discord server, with an optional audit-log reason, to keep your member profile current.

Instructions

Change your own server nickname / server avatar / banner / bio. [PATCH /guilds/{guild_id}/members/@me]

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

Input Schema

NameRequiredDescriptionDefault
bioNo
nickNo
avatarNo
bannerNo
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
pronounsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/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 mutation. The description adds the useful scope constraint that only the caller's own membership can be changed, but says nothing about permission requirements, that omitted fields are left unchanged, or that 'reason' surfaces in the audit log — behavior an agent would want before mutating.

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?

A single front-loaded sentence naming the mutating fields plus the HTTP endpoint in brackets — zero padding, easy to scan, and the scope-defining phrase 'your own' comes first.

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 7-parameter mutation with no output schema and thin annotations, the definition is serviceable but under-informative: it does not cover pronouns/reason parameters, permission prerequisites, or the effect of leaving a field absent versus passing null.

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 only 29%, so the description should compensate; it partially does by enumerating nickname/avatar/banner/bio, but each of those already has a schema description with more detail (including null/empty reset semantics). Pronouns, reason, and guild_id get no treatment in the description at all.

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 names a specific verb ('Change') and an enumerated set of resources (own server nickname, avatar, banner, bio), and the qualifier 'your own' implicitly separates it from modify_guild_member, which acts on other members. The PATCH endpoint reinforces the target resource unambiguously.

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 by 'your own' — the agent can infer this is the self-service profile editor as opposed to the administrative member editor. However, no explicit when-to-use/when-not statement or named alternative (e.g. modify_guild_member for other users) appears in the description.

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