Skip to main content
Glama
wowjinxy
by wowjinxy

get_user_info

Fetch Discord user details by providing a user ID to retrieve profile information and account data.

Instructions

Fetch information about a specific Discord user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function that executes the get_user_info tool, fetching Discord user data and formatting a detailed info response.
        @staticmethod
        async def handle_get_user_info(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
            """Get user information"""
            user = await discord_client.fetch_user(int(arguments["user_id"]))
            
            info = f"""
    **User Information for {user.display_name}**
    
    **Basic Info:**
    - Username: {user.name}
    - Display Name: {user.display_name}
    - ID: {user.id}
    - Bot: {"Yes" if user.bot else "No"}
    - Account Created: {user.created_at.strftime('%Y-%m-%d %H:%M:%S')}
    
    **Avatar:** {user.display_avatar.url if user.display_avatar else "No avatar"}
            """.strip()
            
            return [TextContent(type="text", text=info)]
  • Registers the get_user_info tool in the MCP server's tool list with description and input schema requiring 'user_id'.
    Tool(
        name="get_user_info",
        description="Get detailed information about a Discord user",
        inputSchema={
            "type": "object",
            "properties": {
                "user_id": {
                    "type": "string",
                    "description": "Discord user ID"
                }
            },
            "required": ["user_id"]
        }
    ),
  • Lists 'get_user_info' among core tools to route execution to the corresponding CoreToolHandlers method.
        "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"
    ]
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 'fetches information' but doesn't specify what information is returned (though an output schema exists), whether it requires permissions, rate limits, or error conditions. For a tool with no annotations, this is a significant gap in transparency.

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 any fluff. It's front-loaded and wastes no words, making it easy for an agent to parse quickly.

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 low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks context on usage guidelines and behavioral traits, which are important for a tool in a server with many sibling alternatives. It meets the basic threshold but has clear gaps.

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 compensates by implying the parameter's purpose ('specific Discord user'). It doesn't detail the format of 'user_id' (e.g., string vs. integer), but since there's only one parameter and the description adds meaningful context, it scores above baseline. A perfect score is reserved for explicit parameter explanations.

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 action ('Fetch') and resource ('information about a specific Discord user'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_members' or 'get_server_info' which might also provide user-related data, so it doesn't reach the highest 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. It doesn't mention prerequisites (e.g., needing a user ID), exclusions, or how it differs from sibling tools like 'list_members' that might list multiple users. This leaves the agent with minimal context for selection.

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