Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

discord_logout

Destructive

Remove the saved Discord login from this machine, and set revoke=true to invalidate the token at Discord so this session logs out everywhere it is used.

Instructions

Forget the saved login on this machine. With revoke=true also invalidates the token at Discord (logs this session out everywhere it is used).

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

Input Schema

NameRequiredDescriptionDefault
revokeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds important behavioral detail beyond annotations: it specifies what is removed locally and that revoke=true invalidates the Discord token everywhere the session is used. It does not describe failure or error behavior, but adds substantial value.

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?

Two tight sentences with the local behavior front-loaded and the conditional global effect immediately after. Every phrase contributes to scope and parameter meaning.

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 one-parameter destructive logout tool with no output schema, the description covers the key local versus global distinction and the parameter's effect, while annotations cover the safety profile. Minor details such as error behavior are omitted but are not required for correct invocation.

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 single revoke parameter has 0% schema description coverage, so the description carries the burden and does so well: it explains that revoke=true invalidates the token at Discord and logs the session out everywhere. The default local-only behavior is implied rather than explicitly stated as 'false', which keeps it from a 5.

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 ('Forget the saved login') with clear scope ('on this machine'), and contrasts local-only removal with global token invalidation when revoke=true. It is clear but does not explicitly name or differentiate itself from sibling logout tools.

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?

The conditional phrase 'With revoke=true' clearly frames the tradeoff between a local-only forget and a global Discord logout, giving the agent enough context to choose based on scope. It lacks explicit when-not guidance or named alternatives, so it falls 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