mcp-discord

discord_list_roles

Retrieve all roles in a Discord server to manage permissions, organize members, and configure server settings by viewing role hierarchy and details.

Instructions

List all roles in a guild. Returns role objects sorted by position (highest first).

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

Input Schema

Name	Required	Description	Default
`guild_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return format ('role objects') and sorting behavior ('sorted by position, highest first'), which is valuable context. However, it lacks details on permissions, rate limits, or pagination, leaving gaps for a read operation.

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?

The description is front-loaded with the core purpose in the first sentence and adds behavioral detail in the second. Both sentences earn their place with zero waste, making it highly efficient and well-structured.

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?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is mostly complete. It covers purpose, behavior, and parameter context, but could improve by addressing permissions or error handling, though not strictly required for this simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description adds meaning by clarifying that the single parameter 'guild_id' is used to specify the guild for listing roles. Since there is only one parameter, the baseline is 4, and the description provides adequate context without redundancy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List all roles') and resource ('in a guild'), distinguishing it from siblings like discord_list_channels or discord_list_members. It provides precise scope and verb usage.

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 description implies usage for retrieving roles in a guild, but does not explicitly state when to use this tool versus alternatives (e.g., discord_get_guild for guild info or discord_get_member for member roles). No exclusions or prerequisites are mentioned.

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