Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_roles

Replaces all roles assigned to a Discord member with a specified role set, enabling bulk role updates; requires Manage Roles permission.

Instructions

Replace all roles of a member. 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>",
      "userId": "<userId>",
      "roleIds": "<roleIds>"
    },
    "name": "discord_set_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)
roleIdsYesFull role set; use [] to remove every role

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the critical behavioral fact that this is a full overwrite of the existing role set and that Manage Roles is required. It omits what happens on partial failure, whether the bot's own role hierarchy matters, and the purpose of the audit-log reason.

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 action and followed by the permission requirement. No filler, no repetition of the tool 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 a mutation with no annotations and no output schema, the definition covers the essential action and permission gate but leaves the destructive-write semantics of the overwrite, the reason parameter, and failure behavior to inference. Adequate minimum, with clear gaps.

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 coverage is only 50%, and the description adds nothing about individual parameters. The one genuinely important semantic — that roleIds is the complete set and [] clears all roles — lives in the schema, not the description, and the undocumented reason parameter (audit log) is never explained.

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?

"Replace all roles of a member" gives a specific verb (replace), resource (member's roles), and scope (the full set, not a single role), which implicitly distinguishes it from the add/remove-style sibling. It stops short of naming the alternative tool, so the differentiation must be inferred.

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 permission prerequisite ("Requires Manage Roles") is stated, which is useful context for whether the call will succeed. There is no explicit guidance on when to choose this over discord_add_role or discord_list_roles, so the usage boundary is only implied by the word "Replace."

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