Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_kick_member

Kick a member from a Discord server by providing the guild ID and user ID, with an optional reason; requires Kick Members permission.

Instructions

Kick a member from the server. Requires Kick 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_kick_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavioral burden; it does disclose the required permission, which is genuinely useful for a mutation tool. It omits the key behavioral trait that a kicked user can rejoin the server (unlike a ban), and says nothing about audit-log recording, the effect on the member's roles/messages, or what happens on failure.

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 sentences, zero filler, with the action front-loaded and the prerequisite immediately following. Nothing needs trimming and nothing is buried.

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?

For a destructive, permission-gated mutation with no annotations, no output schema, and partially undocumented parameters, this is too thin. The agent lacks the reversibility story, the semantics of the reason field, and the outcome/error behavior needed to call it confidently.

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 coverage is only 33%: guildId is documented as a snowflake, but userId is merely a $ref to guildId and reason has no description at all. The description adds no meaning about the reason parameter (e.g., that it appears in the audit log) or the required vs optional distinction, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ("Kick a member from the server"), which is unambiguous in isolation. It does not differentiate from close siblings such as discord_ban_member or discord_timeout_member, leaving the agent to infer that kick is the non-permanent removal.

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?

"Requires Kick Members" gives a concrete prerequisite, which is useful context for invocation. However, there is no guidance on when to prefer kick over ban, timeout, or disconnect, and no exclusions or failure conditions are mentioned.

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