Skip to main content
Glama
cappyeo

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

members_get_current_user

Read-onlyIdempotent

Retrieve the bot's own member profile in a guild (nick, roles, joined_at) via simple API calls, avoiding the need for the GUILD_MEMBERS intent.

Instructions

Purpose: Fetch the current bot user's own member entry in a guild via GET /users/@me followed by GET /guilds/{guild.id}/members/{bot.id}.

When to use:

  • Discover the bot's nick and role assignments in a target guild without needing the GUILD_MEMBERS intent.

Returns: {user_id, nick, roles, joined_at}. Structured nick remains raw Discord data; the human-readable text response fences it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYesGuild to inspect

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.28.0
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "joined_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "nick": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "roles": {
-        "items": {
-          "description": "Discord role ID",
-          "pattern": "^\\d{17,20}$",
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "user_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "user_id",
-      "nick",
-      "roles",
-      "joined_at"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "joined_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "nick": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "roles": {
+        "items": {
+          "description": "Discord role ID",
+          "pattern": "^\\d{17,20}$",
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "user_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "user_id",
+      "nick",
+      "roles",
+      "joined_at"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]
  2. First observedv0.22.0

TDQS

A4.3/5.0
Behavior4/5

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

The description adds behavioral detail beyond the annotations by revealing that the tool performs two sequential GET requests and by explaining the difference between structured raw data and the human-readable fenced response. It does not contradict the readOnlyHint or idempotentHint annotations.

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?

The description is compact and well-structured, with labeled sections for purpose, usage, and return value. It front-loads the core purpose and keeps every sentence informative without unnecessary detail.

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

Completeness5/5

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

Given a single parameter, existing annotations, and an output schema, the description covers the essential context: the endpoint chain, the intent-related benefit, and the return shape. Nothing critical is missing for a correct call.

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%, and the description does not add meaningful parameter-level detail beyond what the schema already provides ('Guild to inspect'). This meets the baseline for schema-covered parameters.

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 states a specific verb ('Fetch') and resource ('current bot user's own member entry in a guild'), and clarifies the exact endpoint chain. It is clearly distinguishable from siblings like members_get or users_get_current because it emphasizes 'current bot user's own' member entry.

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

Usage Guidelines4/5

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

It gives a clear when-to-use scenario: discovering the bot's nick and role assignments without needing the GUILD_MEMBERS intent. It does not explicitly name alternatives or exclusions, but the context is unambiguous enough for an agent to decide correctly.

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