Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_login_sessions

Read-only

List the devices and sessions currently logged into a Discord account so you can review active access and identify unfamiliar logins.

Instructions

Devices logged into your account (Settings → Devices). [GET /auth/sessions]

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": "list_login_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the HTTP endpoint and the UI location; it says nothing about what a session entry contains, whether the current session is marked, or ordering, which is the extra value it could have supplied.

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 front-loaded fragment plus an endpoint tag — no wasted prose and the resource leads. The bracketed REST path is arguably developer-facing noise for an agent, which keeps it just under 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and no output schema, the description is nearly sufficient, but it never characterizes the returned session records (device names, timestamps, current-session flag). For a tool whose entire value is the shape of what comes back, one clause on return contents would close the gap.

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 there is no parameter semantics for the description to clarify. Baseline 4 applies; nothing is missing or misleading on this dimension.

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 identifies the resource precisely — devices currently logged into the account — and the parenthetical '(Settings → Devices)' anchors it to a concrete UI concept. The verb is only implied by the tool name rather than stated, and no sibling is named, so it stops short of 5.

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?

Usage is implied by the resource: an agent can infer this is the read path for inspecting active sessions. There is no explicit guidance about when to prefer this over the sibling logout_login_sessions (to revoke) or any stated prerequisites, so it stays at minimum-viable.

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