Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

whoami

Read-only

Verify which Discord account is logged in, whether it is a user or bot, and check live connection status for the gateway, servers, and cached DMs before running other actions.

Instructions

Who is logged in, account type (user/bot), and live connection status (gateway, servers, DMs cached). Start here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/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 structurally. The description adds meaningful context beyond that: it reports live connection state (gateway, servers, DMs cached), telling the agent this is a diagnostic snapshot of session health, not just a static identity lookup.

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?

A single compact sentence that front-loads the core output (who is logged in) and ends with the actionable cue 'Start here.' Every clause conveys distinct information with no filler.

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?

There is no output schema, so the description must characterize return values, which it does for the main fields (account identity, account type, connection/cache status). For a zero-parameter, read-only tool this is sufficient, though it could note the response shape or what a degraded connection status implies.

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 nothing for the description to disambiguate and the baseline of 4 applies. No parameter detail is needed or missing.

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 names the specific information returned: identity of the logged-in account, account type (user/bot), and live connection status across gateway, servers, and DMs. That is far more concrete than a tautology, though the verb is implicit ('Who is logged in') rather than an explicit action verb.

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?

'Start here' signals that this is an entry/orientation call before other operations, which is genuine usage guidance. However, it gives no when-not condition and no explicit alternatives, leaving the routing guidance implied rather than stated.

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