Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_current_user_account

Edit your Discord account fields such as display name, avatar, and bio to update profile details. Use it to change account-level information through a single request.

Instructions

Edit account-level fields (global_name, avatar, bio…). [PATCH /users/@me/account]

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
global_nameNo

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the edit is field-scoped (partial update of named fields) and gives the underlying endpoint, but says nothing about authentication requirements, what the "…" covers, or whether omitted fields are preserved or cleared.

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?

One short sentence plus the HTTP endpoint, front-loaded with the verb and scope; nothing is padded. The ellipsis in "(global_name, avatar, bio…)" is the one imprecision, trading specificity for brevity.

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 low-parameter mutation tool with annotations and no output schema, the description should at minimum explain that this is a partial update, what null means, and that the fields listed beyond the schema are not actually settable here. As written, the mismatch between advertised fields and the one-property schema leaves an agent unsure what it can actually change.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage at the top level (only the string branch of the anyOf is annotated "Display name"), so the description needs to compensate nad it barely does. It names global_name without explaining the null branch (presumably clearing the name), and it advertises avatar and bio which do not exist in the schema — actively misleading about settable inputs.

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 ("Edit") and a scoped resource ("account-level fields"), and the endpoint annotation confirms the target (PATCH /users/@me/account). It is clear what the tool does, though it never explicitly contrasts itself with near-neighbors like modify_current_user or modify_user_profile.

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 only implied through the phrase "account-level fields," which suggests this is the account-settings surface rather than profile, guild-member, or voice-state mutation. There is no statement of when to choose this over the many sibling modify_* tools and no prerequisites or exclusions.

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