Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_whoami

Retrieves the logged-in Discord account's ID, username, tag, email availability, and guild count so agents can verify identity and account context before acting.

Instructions

Details of the logged-in account: id, username, tag, email availability, guild count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discord_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully lists the returned fields, but it does not explicitly state that the operation is read-only, whether authentication is required, or clarify what 'email availability' means; for this simple identity tool that is a gap but not a severe omission.

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 a single front-loaded sentence that efficiently lists the key return fields. It contains no redundant wording and is appropriately sized for a simple zero-parameter tool.

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?

For a zero-argument identity tool with no output schema, the field enumeration covers the essential return values an agent would need. It still omits explicit read-only and authentication context, but the low complexity makes the omission relatively minor.

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 has zero parameters, so no parameter semantics are required. Per the baseline for 0 params, this is adequate.

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?

The description names the resource precisely as the logged-in account and enumerates returned fields such as id, username, tag, email availability, and guild count. It implicitly distinguishes itself from arbitrary-user lookups by saying 'logged-in,' but it does not explicitly differentiate from sibling tools like discord_account_profile or discord_get_user.

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?

The description provides no explicit when-to-use or when-not-to-use guidance, and it does not mention alternative tools for account or user lookup. The only usage signal is implied by 'logged-in account.'

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