Skip to main content
Glama
Oratorian

Discord MCP Server

by Oratorian

Leave Discord Server

discord_leave_guild
Destructive

Remove the bot from a Discord server for good. Provide the guild ID and set confirm to true to proceed.

Instructions

Leave a Discord server (guild). The bot will no longer have access to this server.

WARNING: This is a destructive action. The bot will need to be re-invited to rejoin.

Args:

  • guild_id (string): Discord server/guild ID to leave

  • confirm (boolean): Must be set to true to confirm leaving

Returns: Confirmation message with server details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesMust be set to true to confirm leaving the server
guild_idYesDiscord server/guild ID (snowflake)
Behavior4/5

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

The description adds value beyond the destructiveHint annotation by explaining the consequence (bot loses access) and the need to re-invite. No contradiction with annotations.

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?

The description is concise and well-structured, with a purpose sentence, consequence warning, and a brief args list. No unnecessary words.

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 simple destructive action, the description adequately covers purpose, parameters, consequences, and return value hint. Could be slightly enhanced by mentioning the bot must be in the guild, but overall complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 100% of parameters with clear descriptions. The description repeats this information in a different format without adding new semantic details, so a baseline score of 3 is appropriate.

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 clearly states the tool leaves a Discord server (guild) and that the bot loses access. This is specific and distinguishes it from sibling tools that act on members or channels.

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?

The description includes a warning about destructiveness and the need for re-invitation, but does not explicitly state when to use this tool versus alternatives like kick or ban. No comparison with siblings is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Oratorian/discord-node-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server