Skip to main content
Glama
wowjinxy
by wowjinxy

list_roles

Retrieve all role definitions from a Discord server to manage permissions and organize members effectively.

Instructions

List all roles defined in the Discord server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'list_roles' tool. Fetches guild roles excluding default @everyone, sorts by position descending, formats using _format_role helper, and returns formatted string.
    async def list_roles(server_id: str | int | None = None, ctx: Context = None) -> str:  # type: ignore[override]
        """List all roles defined in the Discord server."""
    
        assert ctx is not None
        bot, config = await _acquire(ctx)
        guild_id = _resolve_guild_id(config, server_id)
        guild = await _ensure_guild(bot, guild_id)
    
        roles = [role for role in guild.roles if role != guild.default_role]
        if not roles:
            return f"{guild.name} has no custom roles."
    
        lines = [f"**Roles for {guild.name} (excluding @everyone):**"]
        for role in sorted(roles, key=lambda item: item.position, reverse=True):
            lines.append(_format_role(role))
    
        return "\n".join(lines)
  • Helper function used by list_roles to format each role's details: name, ID, position, member count, color, flags (managed/hoisted/mentionable), and summarized permissions.
    def _format_role(role: discord.Role) -> str:
        colour = f"#{role.colour.value:06X}" if role.colour.value else "default"
        flags: list[str] = []
        if role.managed:
            flags.append("managed")
        if role.hoist:
            flags.append("hoisted")
        if role.mentionable:
            flags.append("mentionable")
        flag_str = f" ({', '.join(flags)})" if flags else ""
        permissions = _summarize_permissions(role.permissions)
        return (
            f"• {role.name} (ID: {role.id}) – Position: {role.position} – Members: {len(role.members)} – "
            f"Colour: {colour}{flag_str}\n  Permissions: {permissions}"
        )
  • The @server.tool() decorator registers the list_roles function as an MCP tool.
    async def list_roles(server_id: str | int | None = None, ctx: Context = None) -> str:  # type: ignore[override]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't cover critical aspects like permissions required, rate limits, pagination, or what the output contains (though an output schema exists). This leaves significant gaps for a tool that likely requires server access.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse, which is ideal for conciseness.

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?

Given the tool's low complexity (1 optional parameter) and the presence of an output schema, the description is minimally adequate. However, it lacks context about permissions or server access requirements, which are crucial for Discord API tools. With no annotations, it should provide more behavioral details to be fully 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?

The description adds no parameter information beyond what the schema provides. With 0% schema description coverage and 1 parameter (server_id), the description doesn't compensate by explaining the parameter's purpose or usage. However, since there's only one optional parameter and an output schema exists, the baseline is 3, as the schema handles the minimal parameter documentation.

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?

The description clearly states the verb 'List' and the resource 'all roles defined in the Discord server', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_server_info' or 'list_members' which might also provide role information, so it's not a perfect 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing server access), exclusions, or compare it to sibling tools like 'get_server_info' that might include role data, leaving the agent with no usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wowjinxy/mcp-discord'

If you have feedback or need assistance with the MCP directory API, please join our Discord server