Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_guild_member_me

Retrieves your membership details in a Discord server, including nickname, roles, and computed permissions.

Instructions

The account member object in a server: nickname, 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>"
    },
    "name": "discord_guild_member_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 full burden. It does disclose the returned contents (nickname, roles, computed permissions), which implies a read-only lookup, but it says nothing about required permissions, behavior when the account is not a member of the guild, or error conditions.

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 short sentence with no filler and the resource stated up front. It is efficient, though the terseness comes at the cost of the guidance noted in other dimensions.

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?

The tool is simple (one parameter, no nested objects), but with no output schema the description only sketches the returned fields and omits the shape of the roles and permissions data. It is adequate for calling the tool but not fully complete.

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 coverage is 100% with a single documented 'guildId' (Discord snowflake id with a pattern), so the schema already carries the parameter meaning. The description adds no additional semantics such as how the guild is resolved or what happens with an invalid id, so the baseline 3 applies.

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

Purpose3/5

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

The description names the resource ('member object in a server') and the fields it contains ('nickname, roles and computed permissions'), but is a bare noun phrase with no verb, and 'the account' is ambiguous about whether it means the calling account. It also does not distinguish itself from the sibling discord_get_member, so an agent must infer that this returns the caller's own membership rather than an arbitrary member.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative discord_get_member or discord_guild_info. The agent is left to infer usage purely from the tool name's 'me' segment.

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