Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

discord_login

Log in to a personal Discord account by scanning a returned QR image with the Discord mobile app—no password required; the token is saved locally.

Instructions

Log in to your personal Discord account by QR code (no password): returns a QR image to scan with the Discord phone app (Settings → Scan QR Code). Then call discord_login_status with wait=true. The token is saved locally.

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_login"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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, non-destructive, open-world operation; the description adds meaningful context beyond that: authentication is out-of-band via a phone-app QR scan, the call returns an image rather than a token, and the resulting token is persisted locally. It does not cover failure/expiry behavior or what happens if already authenticated, keeping it below 5.

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?

Three short sentences, front-loaded with the action and mechanism, followed by the required next step and the persistence side effect. Every clause carries information an agent needs; the inline menu path is directly actionable for the user.

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-parameter tool with no output schema, the description covers the essential loop: obtain QR, hand to user, then poll discord_login_status. The only gap is edge-case handling, such as an existing session or an expired/unscanned QR, which an agent may need to improvise.

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, so the baseline is 4. The description correctly adds no parameter detail and instead spends its words on the two-step flow, which is the right allocation.

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 ('Log in to your personal Discord account') and pins down the mechanism ('by QR code (no password)'), which separates it from a token/password-based login sibling like discord_login_token. The opening clause alone tells an agent what the tool does and how.

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?

Explicitly sequences the workflow: call this, then call discord_login_status with wait=true. It also tells the human to scan with the phone app via a concrete menu path. It does not state exclusions (e.g., what to do if a session already exists), so it stops short of a 5.

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