mcp-discord-bridge

kick_member

Kick a member from a Discord server by providing guild ID, user ID, and an optional audit log reason.

Instructions

Kick a member from the 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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>"
    },
    "name": "kick_member"
  }
}

Input Schema

Name	Required	Description
`guild_id`	Yes
`user_id`	Yes
`reason`	No	Audit log reason (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits like permission requirements or side effects. It only states 'Kick a member', missing details on audits, reversibility, or return values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence, very concise, but lacks structure or additional context. It is minimally sufficient.

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 tool with no annotations and no output schema, the description fails to provide necessary context about effects, required permissions, or differences from similar operations (e.g., ban).

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 only 33% (reason param described). The tool description adds no extra meaning beyond the schema. The optional reason parameter is the only one with a description in the schema, leaving guild_id and user_id unexplained.

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 ('Kick') and the resource ('a member from the server'), distinguishing it from sibling tools like 'ban_member' or 'timeout_member'.

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?

No guidance on when to use this tool over alternatives (e.g., ban_member for permanent removal, timeout_member for temporary), or any prerequisites or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.