Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_ban_user

Ban a user from a Discord server. Requires Ban Members permission; set confirm to true to execute the ban.

Instructions

Ban a user from a guild (requires your account to have Ban Members).

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>",
      "userId": "<userId>"
    },
    "name": "discord_ban_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
confirmNoSet true to actually perform this destructive action
guildIdYes
deleteMessageSecondsNoDelete this many seconds of the user's recent messages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states the basic action and permission, but omits details like the irreversible nature of bans, impact on user, or audit logging. The confirm parameter hints at destructiveness but is not described in the tool description.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the core purpose and a key prerequisite.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters (2 required), no output schema, and no annotations, the description is inadequate. It fails to explain the confirm safety mechanism, the deleteMessageSeconds parameter, or the behavior/result of a ban. Sibling tools like discord_kick_user have similar complexity but are better documented.

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

Parameters2/5

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

Schema description coverage is 40% (only confirm and deleteMessageSeconds have descriptions). The tool description adds no extra meaning; it does not explain guildId, userId, or the function of confirm (beyond the schema's 'destructive action') or deleteMessageSeconds.

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 action (ban), the resource (user from guild), and a prerequisite (permission). It distinguishes from siblings like discord_kick_user and discord_unban_user.

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?

The description mentions the required permission ('requires your account to have Ban Members'), providing clear context for when the tool is usable. However, it does not explicitly exclude scenarios or reference alternatives.

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