Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Leave server

leave_server
Destructive

Make a Discord bot leave a named server after preview and confirmation, preventing accidental removal.

Instructions

Make the bot leave a server. It can only come back through a new invite from someone with Manage Server, and its own role there is deleted. Always previews first and asks for confirmation. The server must be named: this never falls back to the default one. When two of your bots are in the server, bot says which one leaves.

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": {
      "guild": "<guild>"
    },
    "name": "leave_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
botNoWhich bot to act as, by name, when more than one is configured. Omit to use the default bot, or with a server, the bot that handles it.
guildYesServer name or ID to leave.
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag this as destructive, and the description adds substantive consequences beyond them: the bot can only return via a new invite from someone with Manage Server, and its own role is deleted. It also discloses the preview/confirmation flow and the multi-bot selection behaviour, which are not in 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded with the action and its main consequence. A couple of sentences are slightly compressed in phrasing ('bot says which one leaves'), but nothing is wasted.

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 destructive 3-parameter tool with no output schema, the description covers consequences, prerequisites, confirmation flow, and multi-bot ambiguity. It omits only minor details such as the failure mode when the guild name doesn't match or what the preview returns.

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, but the description adds real meaning beyond the schema: it insists the server be named explicitly rather than defaulted, and explains that the bot parameter only matters when two of the user's bots are in the server. The confirm_token flow is clarified as tied to 'this exact action's preview'.

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?

States a specific verb and resource: 'Make the bot leave a server'. It distinguishes itself from sibling server-management tools (update_server, delete_server_template) by naming the irreversible departure action and its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit prerequisites and scoping: the server must be named, no fallback to the default, and it always previews before confirming. It also explains the multi-bot disambiguation rule, so an agent knows exactly what to supply and when.

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