Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_create_role

Create a Discord role in a guild and set its name, color, hoist, mentionable status, and permissions; requires Manage Roles.

Instructions

Create a role. Requires Manage 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": {
      "guildId": "<guildId>",
      "name": "<name>"
    },
    "name": "discord_create_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNoColor as 0xRRGGBB integer or hex string
hoistNoShow members with this role separately in the member list
reasonNo
guildIdYesDiscord id (snowflake)
mentionableNo
permissionsNoPermission names, for example SendMessages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It discloses the Manage Roles permission requirement, which is useful, but says nothing about side effects, defaults, whether the role is immediately assignable, or what the operation returns.

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?

The description is extremely short and front-loaded, with no wasted wording. However, its brevity reflects under-specification rather than disciplined completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter mutation tool with no annotations and no output schema, this description is far too thin. It includes a key permission requirement but omits behavioral, parameter, and return-value context needed to call the tool confidently.

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?

Schema description coverage is only 57%, and the description adds no parameter-level meaning for guildId, name, color, hoist, mentionable, permissions, or reason. It does not compensate for the undocumented portion of the schema.

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 states a specific verb and resource: "Create a role." This clearly distinguishes creation from sibling operations such as edit, delete, or add role, though it does not explicitly name or differentiate those siblings.

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 only guidance is the permission prerequisite "Requires Manage Roles." There is no explanation of when to choose this tool instead of related tools like discord_edit_role or discord_add_role, nor any exclusions or context about role creation workflows.

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