Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

logout_login_sessions

Log out selected Discord login sessions on other devices using their session ID hashes, revoking access for those sessions.

Instructions

Log out other devices by session hash (session_id_hashes from list_login_sessions). [POST /auth/sessions/logout]

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": {
      "session_id_hashes": "<session_id_hashes>"
    },
    "name": "logout_login_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_id_hashesYessession id hashes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true (i.e., a non-read, non-destructive remote write). The description adds the meaningful scope qualifier 'other devices', implying the caller's own session is not affected, plus the underlying POST path. It does not say whether revocation is reversible, what a partial-success response looks like, or how invalid/stale hashes are handled, so it adds some but not rich behavioral context on top of the annotations.

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 front-loaded sentence that names the action, the selector, and the source of the selector, plus the endpoint tag. Nothing is redundant or padded.

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 tool with no output schema and annotations carrying the safety profile, the description covers purpose, input provenance, and transport. The only notable gap is outcome behavior — success/failure semantics and stale-hash handling — which is minor for this scope.

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?

Schema coverage is 100%, so the baseline is 3; the description goes beyond the schema's bare 'session id hashes' by explaining provenance — the values come from list_login_sessions — which is real guidance for constructing the array. It does not discuss batch semantics (e.g., whether all hashes must be valid or the whole call fails).

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?

The description states a specific verb and resource ('Log out other devices by session hash') and names the exact sibling that produces the required input ('session_id_hashes from list_login_sessions'), so an agent can separate it from list_login_sessions without opening any schema.

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?

It gives a clear procedural prerequisite — obtain the hashes from list_login_sessions first — which is the key routing information. It does not state exclusions or what to do about the current session, so it stops short of full when/when-not guidance.

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