Skip to main content
Glama
Sign In
discp

discp

by SharimAli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

unban_member

Remove a Discord server ban so a user can rejoin. Provide the user ID, optional guild ID, and audit log reason to restore access.

Instructions

Remove a ban from a user, allowing them to rejoin

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": {
      "userId": "<userId>"
    },
    "name": "unban_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason
userIdYesUser ID to unban
guildIdNoDiscord server ID (defaults to DISCORD_GUILD_ID)

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 behavioral burden. It says nothing about required permissions (e.g. Ban Members), what happens if the user is not currently banned, error behavior, or the audit-log side effect implied by the 'reason' parameter.

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?

One short sentence, front-loaded with the action and free of filler. It is appropriately sized for the tool, though its brevity is part of why behavior details are missing.

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?

A state-mutating moderation tool with no annotations, no output schema, and no documented permission or error semantics. For an unban operation the agent needs to know the permission requirements and preconditions, and none are given.

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 all three parameters (userId, reason, guildId) are documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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+resource ('Remove a ban from a user') with the resulting effect ('allowing them to rejoin'). Clear enough to distinguish from ban_member, kick_member, and list_bans, though it never names those siblings to disambiguate.

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 when-to-use guidance, no prerequisites, and no alternatives named. The agent must infer the use case from the tool name alone; siblings like ban_member and remove_timeout offer no routing signal.

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