Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_recent_avatars

Read-only

Retrieve recently used avatars for the authenticated Discord account so you can review or reuse available profile images.

Instructions

List Recent Avatars. [GET /users/@me/avatars]

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": "list_recent_avatars"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered structurally; the description adds essentially nothing on top, only the HTTP verb/path. It does not say whether results are scoped to the calling user, how many entries come back, whether paging exists, or whether the listing changes over time — all live behavior an agent would want.

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?

Two short fragments, front-loaded with the resource name and followed by the endpoint reference. Nothing is padded or redundant, though the endpoint bracket is developer-facing metadata rather than agent-facing guidance.

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

Completeness5/5

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

This is a zero-parameter read-only listing with no output schema and full annotation coverage, so the description does not need to explain inputs or return shape. The stated purpose plus the @me scope is sufficient for an agent to decide whether to invoke it in this straightforward case.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to compensate for; the baseline of 4 applies. The description correctly implies no inputs are needed by omitting any, consistent with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name in title case ("List Recent Avatars") with no elaboration, but the appended endpoint path [GET /users/@me/avatars] does reveal that the avatars belong to the authenticated user (@me) rather than a guild or other user. That scope detail is the only thing distinguishing it from a bare tautology, and it never clarifies what an "avatar" record contains or what makes one "recent".

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives. The sibling delete_recent_avatar strongly suggests a paired lifecycle, but the description does not say to call this first to discover items before deleting, nor does it set any condition for choosing this tool.

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