Skip to main content
Glama
hanweg

mcp-discord

by hanweg

get_user_info

Retrieve detailed information about a Discord user by providing their unique user ID, enabling integration with Discord data in MCP client systems.

Instructions

Get information about a Discord user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesDiscord user ID

Implementation Reference

  • Handler for get_user_info tool: fetches Discord user by ID and returns formatted user information including name, ID, bot status, and creation date.
    elif name == "get_user_info":
        user = await discord_client.fetch_user(int(arguments["user_id"]))
        user_info = {
            "id": str(user.id),
            "name": user.name,
            "discriminator": user.discriminator,
            "bot": user.bot,
            "created_at": user.created_at.isoformat()
        }
        return [TextContent(
            type="text",
            text=f"User information:\n" + 
                 f"Name: {user_info['name']}#{user_info['discriminator']}\n" +
                 f"ID: {user_info['id']}\n" +
                 f"Bot: {user_info['bot']}\n" +
                 f"Created: {user_info['created_at']}"
        )]
  • Registration of the get_user_info tool in list_tools(), including its name, description, and input schema requiring user_id.
    Tool(
        name="get_user_info",
        description="Get information about a Discord user",
        inputSchema={
            "type": "object",
            "properties": {
                "user_id": {
                    "type": "string",
                    "description": "Discord user ID"
                }
            },
            "required": ["user_id"]
        }
    ),
  • Input schema for get_user_info tool: requires a string user_id.
    inputSchema={
        "type": "object",
        "properties": {
            "user_id": {
                "type": "string",
                "description": "Discord user ID"
            }
        },
        "required": ["user_id"]
    }
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 states the action ('Get information') but fails to describe key traits such as whether this is a read-only operation, potential rate limits, authentication requirements, or what happens if the user ID is invalid. For a tool with zero annotation coverage, 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 unnecessary words. It is front-loaded with the core action and resource, making it easy to parse. Every part of the sentence earns its place by clearly conveying the essential function.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns user data. It doesn't specify what information is retrieved (e.g., username, avatar, roles), the response format, or error handling. For a read operation with no structured output documentation, more detail is needed to guide the agent 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 input schema has 100% description coverage, with the 'user_id' parameter clearly documented as 'Discord user ID'. The description does not add any meaning beyond this, as it doesn't elaborate on parameter usage, format, or examples. According to the rules, with high schema coverage, the baseline is 3, which is appropriate here.

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 user'), making the purpose immediately understandable. It distinguishes this from siblings like 'list_members' or 'get_server_info' by focusing on individual user data rather than collections or server metadata. However, it doesn't specify what information is retrieved (e.g., profile, roles, status), keeping it from 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?

No explicit guidance is provided on when to use this tool versus alternatives like 'list_members' or 'get_server_info'. The description implies usage for retrieving data about a specific user, but it lacks context on prerequisites (e.g., needing a user ID) or exclusions (e.g., not for bulk queries). This leaves the agent to infer usage from the tool name alone.

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