Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_unban_member

Lift a ban on a Discord server member by user ID, restoring their access to the guild. Use it to reverse moderation actions when a ban is no longer warranted.

Instructions

Remove a ban. 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_unban_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the required permission, but says nothing about error behavior for an unbanned user, whether the operation is idempotent, whether a reason is recorded to the audit log, or what the response looks like.

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, zero filler, with the core action front-loaded before the prerequisite. The terseness is close to under-specification rather than padding, so it is efficient but not maximally informative.

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 permission-gated mutation with no annotations, no output schema, and an undocumented reason parameter. Given that complexity, the description should state failure semantics and the audit-log role of reason, but it omits both.

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 33%: only guildId carries a description ('Discord id (snowflake)'), which userId inherits via $ref, while the optional reason parameter (max 512 chars) is undocumented beyond its name. The description adds no parameter-level meaning at all, leaving the coverage gap unaddressed.

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 names a specific verb+resource pair ('Remove a ban'), which is the clear inverse of the sibling discord_ban_member and unambiguous about what state change occurs. It stops short of naming or explicitly contrasting the sibling, so it lands at 4 rather than 5.

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?

The permission prerequisite ('Requires Ban Members') gives the agent a real precondition for calling it, and 'Remove a ban' implies the case where a ban already exists. However, there is no explicit when-not guidance, no statement about what happens if the user is not banned, and no named alternative.

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