Skip to main content
Glama

discord_get_member_info

Retrieve detailed Discord member information including roles, permissions, join date, and timeout status for moderation and management purposes.

Instructions

Get detailed info about a member: roles, permissions, join date, timeout status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
user_idYes

Implementation Reference

  • The implementation of the `discord_get_member_info` tool handler, which fetches member details from the guild and returns them as a JSON-formatted string.
    case "discord_get_member_info": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      const member = await guild.members.fetch(args.user_id as string);
      return {
        content: [{
          type: "text", text: JSON.stringify({
            id: member.id, username: member.user.tag, nickname: member.nickname,
            roles: member.roles.cache.filter((r) => r.name !== "@everyone").map((r) => ({ id: r.id, name: r.name })),
            permissions: serializePermissions(member.permissions),
            joinedAt: member.joinedAt?.toISOString(), createdAt: member.user.createdAt.toISOString(),
            bot: member.user.bot, timedOutUntil: member.communicationDisabledUntil?.toISOString() ?? null,
          }, null, 2),
        }],
      };
    }
  • The tool definition and input schema for `discord_get_member_info`.
    {
      name: "discord_get_member_info",
      description: "Get detailed info about a member: roles, permissions, join date, timeout status.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          user_id: { type: "string" },
        },
        required: ["guild_id", "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 it's a read operation ('Get'), implying non-destructive behavior, but lacks details on permissions required, rate limits, error conditions, or response format. This is inadequate for a tool with no annotation coverage.

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 front-loads the core purpose and lists key data points without unnecessary words. Every part adds value, making it appropriately sized for its content.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks parameter explanations, behavioral context like authentication needs, and details on return values. For a tool with two required parameters and no structured support, this leaves significant gaps for an AI agent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It doesn't mention the two required parameters (guild_id and user_id) or explain their semantics, such as what format they should be in or where to obtain them. This leaves critical input details unclear.

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 the resource 'detailed info about a member', specifying what information is retrieved (roles, permissions, join date, timeout status). It distinguishes from siblings like discord_get_guild_info or discord_list_members by focusing on individual member details, though it doesn't explicitly name alternatives.

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 on when to use this tool versus alternatives is provided. It doesn't mention prerequisites like needing guild and user IDs, nor does it compare with similar tools like discord_list_members for broader queries or discord_get_role_members for role-based filtering.

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

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