Skip to main content
Glama
scarecr0w12

discord-mcp

list_permissions

Retrieve all Discord permission names for configuring roles and channel overwrites. This tool provides the complete list of permissions available in Discord's permission system.

Instructions

List all available Discord permission names that can be used for roles and channel overwrites

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_permissions' tool. It extracts permission names from PermissionFlagsBits, categorizes them into groups (general, text, voice, etc.), and returns a JSON-formatted text response listing all available Discord permissions.
      'list_permissions',
      'List all available Discord permission names that can be used for roles and channel overwrites',
      {},
      async () => {
        const permissions = Object.keys(PermissionFlagsBits).filter(
          (key) => isNaN(Number(key))
        );
    
        const categorized = {
          general: [
            'Administrator', 'ViewAuditLog', 'ViewGuildInsights', 'ManageGuild',
            'ManageRoles', 'ManageChannels', 'KickMembers', 'BanMembers',
            'CreateInstantInvite', 'ChangeNickname', 'ManageNicknames',
            'ManageEmojisAndStickers', 'ManageWebhooks', 'ManageGuildExpressions',
            'ViewChannel',
          ],
          text: [
            'SendMessages', 'SendMessagesInThreads', 'CreatePublicThreads',
            'CreatePrivateThreads', 'EmbedLinks', 'AttachFiles', 'AddReactions',
            'UseExternalEmojis', 'UseExternalStickers', 'MentionEveryone',
            'ManageMessages', 'ManageThreads', 'ReadMessageHistory',
            'SendTTSMessages', 'UseApplicationCommands', 'SendVoiceMessages',
          ],
          voice: [
            'Connect', 'Speak', 'Stream', 'UseEmbeddedActivities',
            'UseSoundboard', 'UseExternalSounds', 'UseVAD', 'PrioritySpeaker',
            'MuteMembers', 'DeafenMembers', 'MoveMembers',
          ],
          stage: [
            'RequestToSpeak',
          ],
          events: [
            'CreateEvents', 'ManageEvents',
          ],
          monetization: [
            'CreateGuildExpressions', 'ViewCreatorMonetizationAnalytics',
          ],
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                message: 'Available Discord permissions',
                permissions,
                categorized,
              }, null, 2),
            },
          ],
        };
      }
    );
  • src/index.ts:58-58 (registration)
    Top-level registration call that invokes registerPermissionTools(server), which registers the 'list_permissions' tool among other permission tools.
    registerPermissionTools(server);
  • src/index.ts:15-15 (registration)
    Import of the registerPermissionTools function used to register the permission tools including 'list_permissions'.
    import { registerPermissionTools } from './tools/permission-tools.js';
  • Input schema for 'list_permissions' tool: empty object as it requires no parameters.
    async () => {
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation ('List') but lacks details on behavioral traits such as rate limits, authentication needs, or output format. It adds some context about the data's purpose but is minimal.

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, efficient sentence with no wasted words. It front-loads the purpose clearly and is appropriately sized for a simple tool with no parameters.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the purpose and usage context but lacks details on behavioral aspects like response format or limitations, leaving some gaps for a complete understanding.

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 tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description does not mention parameters, which is appropriate, earning a baseline score of 4 for not adding unnecessary details.

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 verb ('List') and resource ('all available Discord permission names'), specifying their use for 'roles and channel overwrites'. It distinguishes from siblings like 'list_roles' or 'list_channels' by focusing on permission names rather than entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description implies usage context by mentioning 'roles and channel overwrites', suggesting when this tool is relevant (e.g., for configuring permissions). However, it does not explicitly state when to use it versus alternatives or provide exclusions.

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/scarecr0w12/discord-mcp'

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