Discord Server Setup MCP

Overview Schema Source Related Servers Discussions Admin

get_guild_info

Gets detailed information about a Discord server: channels, roles (sorted hierarchically), and settings. Specify guild ID or use the current guild.

Instructions

Gets detailed information about a Discord server (guild), including channels, roles (sorted highest-to-lowest with the bot's hierarchy ceiling), and settings. If no guildId is specified, uses the currently selected guild.

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

Input Schema

Name	Required	Description	Default
`guildId`	No	Guild ID or name (optional, uses current guild if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Feb 11, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses the sorting of roles and mention of hierarchy ceiling, but does not cover error handling, authentication needs, rate limits, or potential side effects. Adequate for a simple read operation but not comprehensive.

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

Conciseness5/5

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

Two sentences with no wasted words. Purpose and behavior are front-loaded. Every sentence adds value.

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

Completeness4/5

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

Given the tool's simplicity (one optional parameter, no output schema), the description covers the returned content (channels, roles, settings) and parameter behavior. Could mention that settings include all guild settings, but overall it is sufficient for an agent to invoke correctly.

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) with 100% schema coverage. The description repeats the schema's explanation about using current guild if not specified, adding no new semantic value. Baseline score of 3 is appropriate.

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

Purpose5/5

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

Clearly states it retrieves detailed information about a Discord server, listing specific elements (channels, roles with sorting detail, settings). Distinguishes from sibling tools that create, delete, or edit guild resources, as this is a read-only information retrieval tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on when this tool is appropriate (getting detailed guild info) and explains the behavior when no guildId is given (uses current guild). Lacks explicit guidance on when not to use or direct comparison to alternatives like list_guilds.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.