Skip to main content
Glama

Moderate member (admin)

discord_admin_moderate_member
Destructive

Moderate a Discord member by user ID: time out, remove timeout, set nickname, kick, ban, or unban. Kick and ban actions require a reason and prior confirmation.

Instructions

Timeout, remove timeout, set nickname, kick, ban or unban a member by user ID. Confirm kicks and bans with the user first. A reason is required for both.

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>",
      "action": "<action>"
    },
    "name": "discord_admin_moderate_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
reasonNoReason, recorded in Discord's audit log
minutesNotimeout: how long (max 28 days)
user_idYesThe member's user ID
nicknameNoset_nickname: new nickname; empty resets it
delete_message_daysNoban: also delete their recent messages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds value beyond that: a confirmation step before kicks/bans, and the fact that a reason is mandatory for both (recorded in the audit log per the schema). It omits whether kicks/bans are irreversible, what permissions the caller needs, and whether timeouts can be lifted after other actions.

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 short sentences, action list front-loaded, then the safety rule. No filler, no restatement of the title, and every clause carries information the agent needs.

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

Completeness4/5

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

For a destructive six-action tool with no output schema, the definition covers the action set, the identifier, the confirmation requirement, and reason mandatory-ness — enough to call it correctly. The remaining gap is that it never states required bot permissions or the irreversibility of kick/ban, which matter for a destructive admin tool.

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 83%, so the schema already explains user_id, reason, minutes, nickname and delete_message_days; the baseline is 3. The description adds one genuinely useful fact not encoded in the schema — that a reason is required for kicks and bans despite 'reason' not appearing in the required array — but says nothing about minutes, nickname reset semantics, or delete_message_days.

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 opens with a precise enumeration of the six moderation actions (timeout, remove timeout, set nickname, kick, ban, unban) applied to 'a member by user ID', which maps one-to-one onto the action enum. An agent can tell this is the member-moderation tool rather than discord_admin_set_member_roles or discord_admin_get_member. It stops short of a 5 because it never names a sibling or explicitly excludes overlapping tools such as discord_admin_bans.

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?

It gives a real procedural rule — 'Confirm kicks and bans with the user first' — which is useful when-to-use guidance for the destructive branches. However, it offers no guidance on selecting this tool over alternatives (roles, automod, message management) and no conditions for choosing among the six actions beyond the enum itself.

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