Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

discord_login_token

Authenticates a saved Discord user or bot token and stores it locally for the session. Use it to connect an AI assistant to your Discord account or bot without a QR-code login.

Instructions

Log in with a token you already have (user token, or "Bot " / type=bot for a bot). Verifies it and saves it locally.

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": {
      "token": "<token>"
    },
    "name": "discord_login_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoToken type (default user; "Bot " prefix implies bot)
tokenYesDiscord token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive operation. The description adds genuinely useful context beyond that: the token is verified (a network round-trip) and then persisted locally, so the agent knows state is written to disk. It does not say what happens on verification failure or where the credential is stored.

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 sentence with the action front-loaded and no wasted wording; the parenthetical carries useful detail compactly. Minor density in the nested quotes/parentheses but nothing that impedes parsing.

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 two-parameter tool with no output schema and annotations covering safety, the description is nearly complete: it explains the token forms, verification, and local persistence. The remaining gap is post-login behavior (session lifetime, how to check status via discord_login_status), which is modest.

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%, so both parameters are already documented, including the enum and the 'Bot ' prefix behavior. The description mainly restates the bot/user token distinction rather than adding new semantics such as format expectations or precedence between the prefix and the type field, so the baseline of 3 applies.

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 states a specific verb and resource: logging in with a pre-existing token, plus the accepted token flavors (user token, "Bot <token>" prefix, or type=bot). It is clear what the tool does, though it never names discord_login or discord_login_status, so the distinction from those siblings must be inferred.

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

Usage Guidelines3/5

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

The phrase 'a token you already have' implicitly signals when this tool is appropriate (you possess credentials rather than gathering them), but there is no explicit when-not statement, prerequisite, or named alternative like discord_login. Usage is implied rather than stated.

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