Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_edit_role

Rename a Discord role, update its color, hoist, mentionable flag, or permission set; requires Manage Roles to apply changes.

Instructions

Rename a role, change its color, hoist, mentionable flag or permissions. 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>",
      "roleId": "<roleId>"
    },
    "name": "discord_edit_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNoColor as 0xRRGGBB integer or hex string
hoistNo
reasonNo
roleIdYes
guildIdYesDiscord id (snowflake)
mentionableNo
permissionsNoReplaces the permission set when provided

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?

With no annotations supplied, the description carries the full behavioral burden; it does add the important Manage Roles permission gate, which is genuine value. However, it omits that this is a partial update (fields not supplied stay unchanged), that permissions fully replaces the existing set, whether changes are logged to the audit log via 'reason', and whether failures are reversible. For a destructive mutation tool with zero annotation coverage these are meaningful gaps.

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?

Two short sentences, front-loaded with the operation and field list, followed by the permission prerequisite. No filler, no restatement of the title or name.

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?

For an eight-parameter mutation tool with no annotations and no output schema, the definition covers the headline fields and the permission gate but leaves the agent guessing about partial-update semantics, permission-set replacement, and the purpose of 'reason'. Adequate to start a call correctly, not complete enough to predict its effects.

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?

Schema coverage is only 38%, so the description must compensate; it names five of the eight parameters and thereby signals what name/color/hoist/mentionable/permissions control. It says nothing about 'reason' (audit-log justification), the roleId target, or the snowflake format of guildId, leaving several low-coverage parameters undocumented in prose.

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?

Names the resource (role) and enumerates the specific mutable fields: name, color, hoist, mentionable, permissions. That clearly separates it from siblings like discord_create_role, discord_delete_role, and discord_set_role_position. It falls short of a 5 only because 'Rename a role' leads, slightly understating that this is a general attribute editor.

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 gives a prerequisite ('Requires Manage Roles') but no guidance on when to choose this over adjacent tools such as discord_set_role_position for ordering or discord_add_role for assignment. Usage is implied by the field list rather than stated as a decision rule.

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