Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_emoji_guild

Read-only

Fetch the guild associated with a custom Discord emoji using its emoji ID to identify which server owns it.

Instructions

Get Emoji Guild. [GET /emojis/{emoji_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": {
      "emoji_id": "<emoji_id>"
    },
    "name": "get_emoji_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
emoji_idYesCustom emoji 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, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the REST path, which together with the name hints that a guild object is returned, but it discloses nothing about the returned guild, permissions required, or emoji-type restrictions.

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 second clause is a raw route string that duplicates what the name and endpoint already imply rather than adding useful information. Nothing is padded, but nothing informative is packed 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 read-only lookup with no output schema, the description should say what is returned (a guild object for the emoji, or a null/error when the emoji is not guild-owned). Neither that nor any behavioral context is provided, leaving the agent with only the name and path to work from.

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 documented parameter (emoji_id, "Custom emoji ID"), so the schema carries the parameter burden. The description adds no additional meaning about the identifier format or acceptance criteria, which is the baseline expectation when coverage is this high.

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 text is essentially a restatement of the tool name ("Get Emoji Guild") plus the raw HTTP route, not an independent statement of purpose. It never explains what a guild of an emoji means or why it differs from the sibling get_guild_emoji, so an agent cannot distinguish them from the text alone.

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?

No usage guidance at all: no when-to-use, no prerequisite, and no mention of when another emoji or guild lookup tool would be preferred. The agent must infer the context entirely from the tool name.

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