Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

leave_guild

Destructive

Leave a Discord server using its guild ID, optionally noting you were only lurking. Use it to exit a guild your account or bot has joined.

Instructions

Leave a server. [DELETE /users/@me/guilds/{guild_id}]

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_id": "<guild_id>"
    },
    "name": "leave_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
lurkingNotrue if you were only lurking
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds essentially nothing beyond that — the HTTP endpoint mapping is the only extra, and it does not explain irreversibility, what is lost on leaving, or whether rejoining is possible.

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?

Two short clauses, front-loaded with the action, with no padding or filler. The bracketed endpoint is mildly redundant but gives a compact API anchor, so little is wasted.

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?

For a two-parameter destructive tool with no output schema, the annotations carry most of the weight, and the description confirms the operation. It nonetheless omits the consequences of the call and the significance of the `lurking` parameter, which an agent would want before invoking a destructive action.

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?

Schema description coverage is 100%, with both `guild_id` and the optional `lurking` flag documented in-schema, so the baseline is 3. The description adds no meaning about what `lurking` changes or when to set it, but it does not need to given the complete schema.

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 gives a specific verb and resource ("Leave a server"), which is unambiguous on its own. It does not, however, distinguish the action from the closely related `delete_guild` sibling, so an agent must reason about the difference between leaving and deleting a server unaided.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite stated (e.g. must be a current member), no warning that the action is irreversible, and no pointer to alternatives such as `delete_guild` or `bulk_leave_group_dms`. The agent is left to infer context entirely from the name.

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