Skip to main content
Glama
hanweg

mcp-discord

by hanweg

get_server_info

Retrieve detailed information about a Discord server by providing its server ID, enabling efficient management and integration with MCP clients.

Instructions

Get information about a Discord server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesDiscord server (guild) ID

Implementation Reference

  • Handler implementation for the 'get_server_info' tool within the call_tool function. Fetches Discord guild information using the provided server_id and returns formatted text content.
    elif name == "get_server_info":
        guild = await discord_client.fetch_guild(int(arguments["server_id"]))
        info = {
            "name": guild.name,
            "id": str(guild.id),
            "owner_id": str(guild.owner_id),
            "member_count": guild.member_count,
            "created_at": guild.created_at.isoformat(),
            "description": guild.description,
            "premium_tier": guild.premium_tier,
            "explicit_content_filter": str(guild.explicit_content_filter)
        }
        return [TextContent(
            type="text",
            text=f"Server Information:\n" + "\n".join(f"{k}: {v}" for k, v in info.items())
        )]
  • Registration of the 'get_server_info' tool in the list_tools() function, defining its name, description, and input schema requiring a 'server_id' string.
    Tool(
        name="get_server_info",
        description="Get information about a Discord server",
        inputSchema={
            "type": "object",
            "properties": {
                "server_id": {
                    "type": "string",
                    "description": "Discord server (guild) ID"
                }
            },
            "required": ["server_id"]
        }
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets information' but doesn't clarify what information is returned, whether it requires permissions, if it's read-only, or any rate limits. This leaves significant gaps for a tool that interacts with an external service like Discord.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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?

Given the complexity of interacting with Discord (an external API with potential auth and rate limits), no annotations, and no output schema, the description is insufficient. It doesn't explain what information is returned, error conditions, or behavioral traits, leaving the agent with significant uncertainty about how to use this tool effectively.

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?

The schema description coverage is 100%, with the single parameter 'server_id' clearly documented in the schema as 'Discord server (guild) ID'. The description doesn't add any meaning beyond this, such as format examples or sourcing tips, but the baseline score of 3 is appropriate since the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('information about a Discord server'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_channels' or 'get_user_info' that also retrieve Discord data, missing the specificity needed for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'list_servers' (which might list multiple servers) and 'get_user_info' (for user data), there's no indication of context, prerequisites, or exclusions for selecting this specific tool.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hanweg/mcp-discord'

If you have feedback or need assistance with the MCP directory API, please join our Discord server