Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_leave_guild

Permanently leave a Discord server by providing its guild ID and setting confirm to true, ensuring the irreversible departure is intentional.

Instructions

Leave a server permanently. Requires confirm: true.

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": {
      "guildId": "<guildId>",
      "confirm": "<confirm>"
    },
    "name": "discord_leave_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Leaving cannot be undone without a new invite.
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it correctly discloses that the operation is irreversible and gated by a confirm flag. It omits operational context an agent would benefit from, notably that a server owner cannot leave without transferring ownership or deleting the server, and what the call returns on success.

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?

Two short sentences, zero filler, with the destructive nature and the confirm requirement both front-loaded. Nothing could be cut without losing a fact.

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 two-parameter, fully described mutation with no output schema, the description covers purpose, permanence, and the confirmation guard. The remaining gap is edge-case behavior (owner restrictions, what happens to memberships/DMs), which would complete it.

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 coverage is 100%, so both parameters are already documented, including the const:true constraint and the snowflake pattern for guildId. The description only restates the confirm requirement and adds no new meaning about either parameter.

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?

"Leave a server permanently" gives a specific verb and resource, and using "server" rather than "thread" implicitly separates it from discord_leave_thread. It does not explicitly name a sibling or contrast behavior, so it stops short of a 5.

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 one prerequisite that matters for invocation (confirm: true) is stated, and "permanently" signals this is a destructive action. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as discord_join_guild for re-joining.

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