discord-mcp

discord_get_my_user

Read-onlyIdempotent

Fetches the bot's own Discord user object—ID, username, global name, avatar, banner, and flags—so you can confirm which account a token belongs to.

Instructions

Fetch the bot's own user object: id, username, global name, avatar, banner and flags. Use it to confirm which account the token belongs to; to look up any other user by ID use discord_get_user. Returns the user object. No special bot permissions. Read-only; safe to retry.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`user`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.2Nov 4, 2026
- removedOutput schema / properties / user / properties / global_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / user / properties / global_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / user / properties / id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
First observedv0.1.0Nov 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds context not present in annotations: that no special bot permissions are needed and that retries are safe. It stops short of describing rate limits or caching behavior, so it is strong but not fully rich.

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?

Front-loaded with the action and returned fields, then usage, then permissions and safety. Slightly redundant in that the field list already implies the return, and "Read-only; safe to retry" mostly restates the annotations, but every sentence remains short and scannable.

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?

An output schema exists, yet the description still names the key fields, so nothing an agent needs is missing. Permissions, safety, and the sibling alternative are all covered, which is more than enough for a zero-argument read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is no parameter meaning the description needs to supply. It correctly avoids inventing inputs, and the schema's additionalProperties=false matches the no-argument contract.

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?

States a specific verb and resource ("Fetch the bot's own user object") and enumerates the returned fields (id, username, global name, avatar, banner, flags). It explicitly distinguishes itself from the sibling discord_get_user, which looks up other users by ID, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ("confirm which account the token belongs to") and an explicit alternative with the condition that selects it ("to look up any other user by ID use discord_get_user"). No inference is required about when this tool applies.

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