Skip to main content
Glama

Member details (admin)

discord_admin_get_member
Read-only

Retrieve a Discord member's roles, nickname, join date, account age, timeout status, and avatar by user ID.

Instructions

One member's roles, nickname, join date, account age, timeout status and avatar.

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": {
      "user_id": "<user_id>"
    },
    "name": "discord_admin_get_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe member's user ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 and openWorldHint=true, so safety is covered. The description adds value by disclosing the returned field set (including derived data like account age and timeout status), but says nothing about permission requirements, behavior for unknown/deleted IDs, or error cases.

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?

A single front-loaded sentence fragment naming the resource first and then the fields; no filler. It is terse to the point of being a field list rather than prose, but nothing is wasted.

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 description correctly compensates by enumerating the returned fields, which is the main thing an agent needs. Remaining gaps (auth/permission needs, error behavior for invalid or departed members) are modest for a simple single-record read.

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?

Only one parameter exists and schema description coverage is 100% (user_id documented with an ID pattern), so the schema fully carries parameter meaning. The description adds nothing beyond it regarding ID format or lookup semantics.

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 names a specific resource (one member) and enumerates exactly what it returns: roles, nickname, join date, account age, timeout status, avatar. An agent can tell this is a single-member read, distinct from list-style siblings, though no sibling is named explicitly.

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?

The singular framing ("One member's...") implies use when you already have a user ID and need full profile data, versus a listing call, but there is no explicit when-to-use, when-not, or named alternative such as discord_admin_list_members.

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