Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_sticker

Read-only

Retrieve a Discord sticker by its sticker ID. Use it to fetch sticker details such as name, format, and image URL for display or processing.

Instructions

Get Sticker. [GET /stickers/{sticker_id}]

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": {
      "sticker_id": "<sticker_id>"
    },
    "name": "get_sticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
sticker_idYesSticker ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety behavior is covered structurally. The description adds nothing beyond an HTTP path: no mention of CDN/asset data, whether the sticker may be deleted or unavailable, or what a caller gets back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the verb, with the endpoint isolated in brackets, so nothing is wasted. However, the brevity reflects under-specification rather than economy of expression.

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 single-parameter read tool with full annotations, full schema coverage, and no output schema, the minimum an agent needs to invoke it is present. The definition nonetheless omits what resource this returns and how it relates to guild/scoped sticker tools, which is the meaningful remaining gap.

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 100% with a single required sticker_id parameter, so the schema already carries the parameter burden. The description adds no syntax, format, or sourcing detail, which is the expected baseline for this coverage level.

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

Purpose2/5

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

"Get Sticker" simply restates the tool name, and the bracketed route [GET /stickers/{sticker_id}] is the only added information. It gives no hint of how this differs from siblings like get_guild_sticker, get_sticker_guild, or get_sticker_pack, so an agent cannot distinguish a global sticker fetch from the guild-scoped variants.

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 stated prerequisites, and no mention of alternatives. The definition leaves the agent to infer entirely from the tools' names that guild-scoped stickers should go to get_guild_sticker instead.

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