Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get member details

get_member
Read-onlyIdempotent

Retrieve full details for one Discord server member, including names, roles, join dates, timeout, voice status, permissions, and bot moderation capabilities based on role hierarchy.

Instructions

Full details of one server member: names, account and join dates, all roles, timeout, voice channel, boosting, key permissions, and whether the bot can kick/ban/timeout them (role hierarchy).

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": {
      "member": "<member>"
    },
    "name": "get_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
memberYesMember: user ID, <@mention>, or name (username, display name or nickname).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the shape of the returned data and, notably, that permission results reflect role hierarchy as evaluated for the bot itself — a non-obvious behavioral detail. It stops short of describing failure modes (unknown member, missing guild).

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?

A single front-loaded sentence that names the resource first and then lists the returned fields, with zero filler or repetition of the title. The parenthetical "(role hierarchy)" efficiently explains why the kick/ban/timeout flags are trustworthy.

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 and only two simple parameters, the description carries the return-value burden and does so by enumerating fields, which is what an agent needs to decide whether to call it. Minor gaps remain around error behavior and required bot permissions, but nothing essential to correct invocation is missing.

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 the guild and member parameters documented including accepted formats (user ID, <@mention>, username/display name/nickname) and the DISCORD_GUILD_ID fallback. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Full details of one server member") and then enumerates the exact payload: names, account and join dates, roles, timeout, voice channel, boosting, key permissions, and kick/ban/timeout capability via role hierarchy. The singular "one server member" cleanly separates it from list_members and search-style siblings.

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: fetching a single member's full profile suggests use when you already have a member identifier, and "whether the bot can kick/ban/timeout them" hints at moderation pre-checks. However, there is no explicit when-to-use statement, no mention of when list_members would be preferable, and no note that a guild must be resolvable.

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