Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

reconnect_gateway

Reconnect the live Discord gateway when live tools report it is not ready, restoring normal message, presence, and voice operations.

Instructions

Reconnect the live gateway connection (use if live tools say the gateway is not ready).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already mark this as non-readOnly, non-destructive, and open-world, so the agent knows it changes connection state safely. The description adds the trigger condition but doesn't say what actually happens on reconnect — whether it drops in-flight live sessions, whether it blocks until ready, how long it takes, or whether repeated calls are harmful. For a state-changing connection operation, that is a meaningful remaining gap.

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 with the action first and the trigger condition in parentheses. No redundant wording or 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?

For a zero-parameter, non-destructive connection action, action plus trigger is nearly everything an agent needs. The main omission is post-call behavior — whether reconnection is synchronous, what indicates success, and whether retries are safe — which would round this out.

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 to document; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs.

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: 'Reconnect the live gateway connection.' An agent immediately knows this re-establishes a gateway session rather than performing a Discord API data operation like the sibling tools. It does not explicitly differentiate itself from any sibling, but none of the listed siblings perform gateway reconnection.

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?

Includes a concrete trigger condition: 'use if live tools say the gateway is not ready.' That is explicit when-to-use guidance tied to an observable signal. It stops short of saying when not to use it (e.g., don't retry in a tight loop, don't call if the gateway is already connected), so not 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