Skip to main content
Glama
Sign In
discp

discp

by SharimAli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_bans

Retrieve banned users from a Discord server with their ban reasons. Specify a guild ID and result limit to review moderation history.

Instructions

List banned users from the server with ban reasons

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (1-100, default: 50)
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 does reveal that ban reasons are returned, which is useful context, but it says nothing about pagination despite a limit parameter, permission requirements, or whether the call is read-only/safe. For a zero-annotation tool this is a meaningful gap.

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?

A single efficient sentence with the key noun and the notable return detail front-loaded; nothing is wasted, though it is terse enough to feel under-filled.

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 query tool with no annotations and no output schema, the description covers the core purpose and return content. It omits pagination/limit behavior and permission prerequisites, which an agent arguably needs before invoking a 100-item-capped listing call.

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 both parameters (limit, guildId) are fully documented with defaults and ranges, so the baseline of 3 applies. The description adds no semantics beyond the schema, such as ordering of results or what limit counts against.

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 (List) and resource (banned users) and adds the returned payload (ban reasons), so it is immediately distinguishable from ban_member, unban_member and get_ban_info. It stops short of explicitly naming those siblings as alternatives, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no statement of when to prefer this over get_ban_info (single ban lookup) or list_members. The agent must infer that this is the bulk-listing counterpart to get_ban_info.

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