discord-admin-mcp

list_roles

Retrieve all roles in a Discord server with their IDs, names, permissions, and positions to simplify role administration.

Instructions

List all roles in a Discord server with their IDs, names, permissions, and positions.

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_roles"
  }
}

Input Schema

Name	Required	Description	Default
`guild_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, and the description does not mention side effects, read-only nature, permission requirements, or error scenarios. Since the description carries the full burden, it fails to disclose potential behavioral aspects.

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 a single, focused sentence that efficiently conveys the tool's purpose and the returned fields. There is no redundant or extraneous information.

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?

The description provides basic return information (IDs, names, permissions, positions) but lacks details on response format, possible errors, or parameter usage. Given the tool's simplicity, it is moderately complete but leaves gaps for a new agent.

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?

The only parameter (guild_id) has no schema description, and the tool description does not explain what it represents or how it is used. With 0% schema coverage, the description must compensate, but it only implies the server context without clarifying the parameter.

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 explicitly states the action (list all roles) and the resource (Discord server), along with the specific data returned (IDs, names, permissions, positions). It clearly distinguishes from sibling tools like list_channels or get_guild_info.

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 when to use it (when you need role information for a server) but does not explicitly mention alternatives or provide contextual guidance like 'use this when you need role details'. It lacks a comparative note found in higher-scoring examples.

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

Deploy Server