Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_ban

Read-onlyDestructive

Check whether a user is banned from a Discord server and retrieve the ban reason using guild and user IDs.

Instructions

Check whether a user is banned (and why). [GET /guilds/{guild_id}/bans/{user_id}]

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": "get_guild_ban"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description's main addition is that the response reveals the ban reason ("and why"), which matters since no output schema exists. It does not disclose the not-banned case (likely a 404/error), permission requirements, or the odd destructiveHint=true flag.

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 compact clauses, front-loaded with the outcome before the endpoint reference. The bracketed path is mildly redundant with the schema but cheap and confirms the exact resource shape.

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

Completeness3/5

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

For a simple two-parameter read tool with no output schema, the description covers the core outcome (ban status plus reason) but leaves notable gaps: behavior for non-banned users, error shape, and permission expectations. Adequate but not complete.

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 coverage is 100% with both required parameters documented as "User ID" and "Server (guild) ID", so the schema does the heavy lifting. The description adds only the endpoint path template, no extra meaning about formats or ID types beyond the schema.

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?

"Check whether a user is banned (and why)" states a specific verb and resource, and the bracketed endpoint path pins down that it operates per-guild/per-user. It is clearly distinguishable from write-path siblings like ban_member, though it never names an alternative.

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?

Usage is only implied: an agent can infer this is the lookup to run before or after ban_member. There is no explicit when-to-use/when-not-to-use guidance, no note about what happens for a non-banned user, and no mention of prerequisites such as permissions.

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