Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_guild_info

Use a guild ID to retrieve a Discord server's channels, roles, and emoji summary for inspecting server structure and permissions context.

Instructions

Server details with channels, roles and emoji summary.

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": {
      "guildId": "<guildId>"
    },
    "name": "discord_guild_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden. It hints at the content of the response (channels, roles, emoji summary) but never says this is a read-only operation, what permissions are required, or whether the response is large/paginated — gaps that matter for a guild-wide aggregate fetch.

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 six-word sentence with no filler, and the resource is front-loaded. It is terse to the point of being under-specified rather than padded, so it scores well on structure but not perfectly on informative density.

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 simple one-parameter read with no output schema and no annotations, the description does sketch the return contents, which is the most important thing to convey. It still omits read-only/safety semantics and permission requirements, leaving meaningful gaps for an agent deciding whether to call it.

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?

Only one parameter (guildId) exists and the schema describes it fully as a Discord snowflake with a regex pattern, so coverage is 100%. The description adds no further meaning about the identifier or how to obtain it, so the baseline of 3 applies.

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 names the resource (server/guild) and enumerates the returned sub-resources (channels, roles, emoji summary), so an agent can infer it retrieves guild metadata. However, there is no verb at all — it is a noun phrase — and no explicit differentiation from siblings such as discord_channel_info or discord_get_user beyond the word 'Server'.

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 statement of when to use this tool, no prerequisites (e.g., bot must be a member of the guild), and no pointer to alternatives for related lookups. The agent must infer usage entirely from the name and the one required parameter.

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