Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_ban_member

Bans a user from a Discord server and optionally deletes recent messages; requires the Ban Members permission.

Instructions

Ban a user from a server. Requires 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_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)
deleteMessageSecondsNoDelete this many seconds of recent messages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the required permission (Ban Members), which is genuine operational context, but it omits that a ban is persistent and reversible only via unban, that it can be applied to users who are not currently members, and any failure conditions.

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 sentences with no wasted wording, and the core action is front-loaded before the permission note. The terseness is a completeness problem rather than a structural one.

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?

This is a destructive, irreversible-by-the-caller mutation with no annotations and no output schema, yet the description covers only the action and a permission requirement. It should say the ban persists until explicitly lifted and explain the optional message-purge parameter, which is the most consequential choice in the call.

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 50%: guildId documents the snowflake format and deleteMessageSeconds explains its effect, but userId is only a $ref and reason has no description. The tool description mentions none of the four parameters, so it does not compensate for the gap or clarify how reason is surfaced or how deleteMessageSeconds interacts with the ban.

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 states a specific verb and resource ("Ban a user from a server"), so an agent immediately knows the operation. It does not differentiate itself from close siblings such as discord_kick_member, discord_timeout_member, or discord_unban_member, leaving the agent to infer the distinction from names alone.

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?

"Requires Ban Members" is a permission prerequisite rather than guidance on when to choose this tool over kick, timeout, or unban. There is no statement of when to use it, when not to, or which sibling handles the adjacent case.

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