Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_kick_member

Kicks a specified user from a Discord server by user ID, with an optional audit log reason and default active server handling.

Instructions

Kick a member from a server.

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": {
      "user_id": "<user_id>"
    },
    "name": "discord_kick_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason.
user_idYesUser ID to kick.
guild_idNoServer ID (defaults to active server).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'kick' but does not explain that this is destructive and irreversible from the server's perspective, that the user can rejoin with a new invite, what happens to their messages, or what permissions the bot requires.

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?

The description is a single, front-loaded sentence with no wasted words. It is structurally sound, though its extreme brevity leaves important operational details unstated.

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 guild-management action with no annotations and no output schema, the description is too thin. It omits permissions, irreversibility, audit logging implications, and how this differs from banning.

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%, and the schema documents user_id, guild_id, and reason sufficiently. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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: 'Kick a member from a server.' An agent can immediately understand the action. However, it does not differentiate this from the sibling tool discord_ban_member, which is a materially different removal action.

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 guidance on when to use kick instead of ban or other member management tools, nor any mention of prerequisites such as needing the Kick Members permission, role hierarchy constraints, or whether the target can rejoin.

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