Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_roles

Read-only

Retrieve all roles in a Discord server with their permissions using the server ID. Inspect role details and permission settings before managing members or channels.

Instructions

List all roles in a server (with permissions). [GET /guilds/{guild_id}/roles]

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

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds only that results carry permissions, and says nothing about ordering, inclusion of the default @everyone role, or result size.

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?

Very short and front-loaded: the purpose comes first, with the REST route appended as a secondary hint. The bracketed endpoint path is redundant for an agent but does not crowd out anything essential.

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?

For a single-parameter read tool with full annotation coverage and no output schema, the definition says enough to call it correctly. Minor gaps remain around what the returned role objects contain beyond permissions and whether the default role is included.

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?

There is a single parameter with 100% schema description coverage ('Server (guild) ID'), so the schema already carries the semantics. The description adds no format or sourcing guidance beyond what the schema provides, which is the expected baseline.

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 plus resource ('List all roles in a server') and adds the notable detail that permission data is included. It is clearly distinct from the sibling set_member_roles, though it does not explicitly contrast with list_guild_role_members, which could be confused with it.

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 by the verb 'List all' — there is no statement of when to prefer this over list_guild_role_members or when role data is needed. No prerequisites (e.g., requiring guild_id and access to the guild) are given.

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