Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_get_member

Fetches one Discord server member using guild and user IDs, returning roles and computed permissions.

Instructions

Get one member of a server, including roles and computed permissions.

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": {
      "guildId": "<guildId>",
      "userId": "<userId>"
    },
    "name": "discord_get_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the payload shape ('roles and computed permissions'), which is real information beyond the tool name. It is silent on permission/intent requirements, cache vs live fetch, and what happens when the user is not a member, all of which matter with zero 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?

One short sentence, front-loaded with the verb and resource, with the returned-data hint appended. No filler or redundancy.

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

Completeness3/5

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

For a two-parameter read tool with no annotations and no output schema, telling the agent what comes back is the key missing piece and it is present. But prerequisites, failure modes, and parameter meaning remain unstated, so it is only minimally adequate.

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?

At 50% schema coverage the description should compensate for the thin parameter documentation, but it mentions neither guildId nor userId nor the snowflake format. The only parameter meaning comes from the schema's '$ref' to the 'Discord id (snowflake)' description.

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?

Clear specific verb+resource: 'Get one member of a server' plus what the result includes (roles, computed permissions). It implicitly distinguishes itself from the global user lookup (discord_get_user) by scoping to a server, but never names a sibling alternative explicitly.

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 when-to-use guidance, no prerequisites (e.g., bot must share the guild), and no mention of when to prefer discord_get_user or discord_guild_member_me instead. Usage is only inferable from the required guildId+userId pair.

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