Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_sticker_guild

Read-only

Retrieves the Discord guild associated with a specific sticker ID, helping identify which server a sticker belongs to.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
sticker_idYesSticker ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/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 the safety profile is covered. The description adds nothing beyond the endpoint path — no note on what is returned, whether a sticker can lack a guild (error case), or any permission requirement.

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-loaded, but the brevity comes at the cost of substance — the entire content is the name plus a route. Nothing wasteful, yet nothing that earns extra credit either.

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 simple single-parameter read tool, the annotations and schema cover most needs, but the description never explains what a "sticker guild" relationship is or what the caller receives. Given the ambiguous sibling get_guild_sticker, that omission is a real gap for correct tool selection.

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% for the single sticker_id parameter, so the schema already does the documenting work. The description adds no additional meaning such as ID format or example values, but the baseline of 3 applies when the schema is fully described.

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?

The description restates the tool name ("Get Sticker Guild") and appends the HTTP route, which is closer to a tautology than an explanation. It does not clarify the distinction from the adjacent sibling get_guild_sticker, leaving an agent unsure whether this returns the guild that owns a sticker or the reverse relationship.

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 guidance on when to use this tool versus get_guild_sticker, get_sticker, or get_sticker_pack. No prerequisites, no conditions, no exclusions are stated.

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