Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_current_user

Update your own Discord account profile by changing username, display name, avatar, banner, bio, pronouns, or accent color to keep your identity current.

Instructions

Edit your account: username (needs password), display name (global_name), avatar, banner, bio, accent colour… [PATCH /users/@me]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "modify_current_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNo
emailNoemail
flagsNoFlags bitfield
avatarNo
bannerNo
passwordNopassword
pronounsNo
usernameNoUsername
avatar_idNoavatar id
email_tokenNoemail token
global_nameNo
accent_colorNo
new_passwordNonew password
date_of_birthNodate of birth (ISO8601 time)
nameplate_sku_idNo
avatar_descriptionNo
display_name_colorsNo
display_name_font_idNo
display_name_effect_idNo
avatar_decoration_sku_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation safety profile is partly covered. The description earns credit for the operational note that changing username 'needs password', which is behavior beyond the structured fields, plus the PATCH endpoint. It does not say whether unspecified fields are preserved, what happens on partial failure, or anything about rate limits, leaving it adequate but not rich.

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 that lists the most important fields first and ends with the endpoint, with no redundant wording. The trailing ellipsis is slightly sloppy for a 20-parameter tool, since it leaves the impression that the listed fields are the whole story.

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 20-parameter mutation endpoint with no output schema, the description is too thin: it does not explain partial-update semantics, whether null clears a field (only the schema's avatar entry says so), or what the call returns. The annotations carry the safety profile, but the behavioral surface of such a broad edit tool is largely undocumented.

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?

With 20 parameters and only 40% schema description coverage, the schema leaves many fields underexplained, so the description must compensate. It partially does: it maps the human term 'display name' to the 'global_name' field and flags the password requirement for username changes, but 14 parameters (flags, avatar_id, email_token, nameplate_sku_id, display_name_colors/font/effect) get no clarification from either source.

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 ('Edit your account') and names the primary editable fields (username, display name, avatar, banner, bio, accent colour), so an agent knows what the tool does. It does not, however, distinguish itself from the strongly overlapping sibling 'modify_current_user_account' (or 'modify_user_profile'), leaving the boundary unclear.

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

Usage Guidelines2/5

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

The description offers no explicit when-to-use or when-not-to-use guidance and names no alternative. Given that 'modify_current_user_account' exists as a near-identical sibling, the absence of routing guidance is a real gap rather than a minor omission.

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