Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

discord_login_status

Read-only

Check or wait for the QR-code login started with discord_login to confirm whether your Discord account session was authorized. Returns the status of the pending scan or confirmation.

Instructions

Check (or wait for) the QR-code login started with discord_login.

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

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~110s for the scan/confirmation
login_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the polling/waiting behavior and its link to discord_login, but says nothing about what happens on timeout, whether the call blocks the agent, or how to interpret a pending versus failed state. With annotations carrying the safety profile, this is adequate but thin.

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?

One short sentence, front-loaded with the verb and the resource, with the dependency on discord_login stated inline. No filler and nothing to trim.

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, read-only status tool with no output schema, the definition covers what the tool does and when it is used. The remaining gaps are the undocumented login_id parameter and the absence of any hint about what status states the agent should expect in the response.

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

Parameters2/5

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

Schema coverage is only 50%: wait is documented in the schema ('Wait up to ~110s'), but login_id has no description anywhere. The description says nothing about login_id's role, whether it is required when multiple logins are pending, or how the returned state is keyed. It therefore fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Check (or wait for) the QR-code login') and ties it explicitly to the sibling that initiates it, discord_login, so an agent can tell it apart from the start-login tool. It stops short of distinguishing it from related session tools, but the core purpose is unambiguous.

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 parenthetical '(or wait for)' and the reference to discord_login imply the intended flow: call after discord_login to poll, optionally blocking. No explicit when-not guidance, no mention of the alternative of re-initiating login or using other session tools, and nothing on what to do if login_id is stale.

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