Skip to main content
Glama
wowjinxy
by wowjinxy

get_server_info

Retrieve detailed information about a Discord server, including channels, roles, and member data, to manage and analyze server structure.

Instructions

Retrieve detailed information about a Discord server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implements the execution logic for retrieving detailed Discord server information using the discord_client.fetch_guild method and formatting it into a structured text response.
        @staticmethod
        async def handle_server_info(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
            """Get server information"""
            guild = await discord_client.fetch_guild(int(arguments["server_id"]))
            
            # Get additional info
            owner = await discord_client.fetch_user(guild.owner_id) if guild.owner_id else None
            
            info = f"""
    **Server Information for {guild.name}**
    
    **Basic Info:**
    - ID: {guild.id}
    - Owner: {owner.name if owner else "Unknown"}
    - Member Count: {guild.member_count}
    - Created: {guild.created_at.strftime('%Y-%m-%d %H:%M:%S')}
    
    **Settings:**
    - Verification Level: {guild.verification_level.name}
    - Content Filter: {guild.explicit_content_filter.name}
    - Boost Level: {guild.premium_tier}
    - Boost Count: {guild.premium_subscription_count}
    
    **Channels & Roles:**
    - Channels: {len(guild.channels)}
    - Roles: {len(guild.roles)}
    - Emojis: {len(guild.emojis)}
    
    **Features:** {', '.join(guild.features) if guild.features else 'None'}
            """.strip()
            
            return [TextContent(type="text", text=info)]
  • Defines the input schema, description, and parameters for the get_server_info tool, requiring a server_id string.
    Tool(
        name="get_server_info",
        description="Get detailed information about a Discord server",
        inputSchema={
            "type": "object",
            "properties": {
                "server_id": {
                    "type": "string",
                    "description": "Discord server (guild) ID"
                }
            },
            "required": ["server_id"]
        }
    ),
  • Registers and routes calls to the get_server_info tool by including it in core_tool_names and dispatching to the corresponding handler method in CoreToolHandlers.
    core_tool_names = [
        "get_server_info", "list_servers", "get_channels", "list_members",
        "get_user_info", "send_message", "read_messages", "add_reaction",
        "add_multiple_reactions", "remove_reaction", "moderate_message",
        "create_text_channel", "delete_channel", "add_role", "remove_role"
    ]
    
    if name in core_tool_names:
        handler_method = f"handle_{name}"
        if hasattr(CoreToolHandlers, handler_method):
            return await getattr(CoreToolHandlers, handler_method)(discord_client, arguments)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieving 'detailed information' but does not specify what details are included, whether it's a read-only operation, permission requirements, rate limits, or error handling. This leaves significant gaps for a tool that interacts with external data.

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 is front-loaded and appropriately sized for a simple retrieval tool.

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?

Given the tool's complexity is low (a read operation with one parameter) and an output schema exists, the description is somewhat complete but lacks behavioral details. Without annotations, it should provide more context on what 'detailed information' entails and usage scenarios to fully guide the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, but the description implies the parameter is for identifying a specific server. Since there is only one parameter, the baseline is high, and the description adds context by indicating the tool focuses on a Discord server, though it does not detail the parameter's format or optionality.

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 'retrieve' and the resource 'detailed information about a Discord server', making the purpose evident. However, it does not differentiate from sibling tools like 'list_servers' or 'get_user_info', which could provide related but different information.

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 guidance is provided on when to use this tool versus alternatives such as 'list_servers' for a broader overview or 'get_user_info' for user-specific data. The description lacks context on prerequisites or exclusions, leaving usage unclear.

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

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/wowjinxy/mcp-discord'

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