Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_avatar

Set a Discord account avatar from an HTTPS image URL or data URI, letting agents update profile images directly.

Instructions

Set the account avatar from an image URL or data URI.

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": {
      "url": "<url>"
    },
    "name": "discord_set_avatar"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL or data: URI of the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that the image may come from an https URL or a data URI, which is real behavioral content, but it omits that the existing avatar is replaced, any size/format constraints, and whether Discord rate limits or elevated auth apply.

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 no filler or redundancy. It is efficient; the only shortcoming is that brevity comes at the cost of the behavioral detail noted above rather than from excess wording.

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

Completeness4/5

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

For a one-parameter tool with complete schema coverage and no output schema, the definition covers what the tool does and the acceptable input source. The remaining gaps (replacement semantics, auth requirements) are minor at this complexity level but not entirely negligible.

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 coverage is 100% and the single parameter is fully documented as an https URL or data: URI. The description restates that same constraint rather than adding syntax examples, accepted image formats, or size expectations, so the baseline 3 applies.

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?

The description gives a specific verb ("Set") and a specific resource ("the account avatar"), and the image-source clause makes the operation unambiguous. It does not name sibling tools such as discord_set_banner or discord_set_accent_color, but "avatar" alone distinguishes it clearly within that family.

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 stated: reading "Set the account avatar" tells an agent this changes the current user's profile picture, but there is no explicit when-to-use guidance, no prerequisite (auth/permission) note, and no mention of how this differs from related profile setters.

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