Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_member

Read-only

Retrieves one Discord server member's roles, nickname, join date, and timeout status using guild and user IDs to inspect membership details.

Instructions

Get one member of a server (roles, nickname, join date, timeout). [GET /guilds/{guild_id}/members/{user_id}]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>"
    },
    "name": "get_guild_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the payload shape (roles, nickname, join date, timeout), which is useful, but says nothing about failure modes (e.g. user not a member) or permission requirements, which matter for an open-world read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence front-loads the action and the return fields, followed by the raw endpoint annotation. The bracketed route is terse and useful for API-literate agents, though it is arguably redundant with the prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the field list in the description does real work in telling the agent what comes back. For a simple two-parameter read tool that is largely sufficient, with only error/permission behavior left unstated.

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?

Schema description coverage is 100%, with both guild_id and user_id documented in the schema, so the baseline of 3 applies. The description adds no format or constraint detail beyond restating that the lookup targets a server and a member.

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 states a specific verb and resource ('Get one member of a server') and enumerates the returned fields (roles, nickname, join date, timeout), so the agent knows exactly what is retrieved. It does not explicitly contrast with the nearby sibling get_current_guild_member, so the distinguishing line is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the required guild_id + user_id pair signals 'fetch a single member by identity'. There is no explicit when-to-use, when-not-to-use, or named alternative such as get_current_guild_member for the calling user.

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

Deploy Server

Other Tools