Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_member_roles

Replaces a Discord member's entire role list with specified role IDs and an optional audit log reason to update permissions in one call.

Instructions

Replace a member's whole role list.

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>",
      "user_id": "<user_id>",
      "role_ids": "<role_ids>"
    },
    "name": "set_member_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason
user_idYes
guild_idYes
role_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the mutating nature is covered structurally. The description adds one genuinely useful behavioral fact — that the operation is a full overwrite rather than an incremental addition — but says nothing about what happens to omitted roles, permission requirements, or the response.

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?

A single front-loaded sentence with zero filler, which is efficient. The extreme brevity is a shortfall in coverage rather than in conciseness, so it is not penalized here.

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 four-parameter mutating tool with no output schema and 25% schema coverage, the definition is too thin. It omits the audit-log reason parameter entirely and gives no behavioral context about role removal or required permissions.

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 25%, with just the 'reason' audit-log field documented in the schema. The description partially compensates by clarifying that role_ids is a complete replacement set rather than a delta, but guild_id and user_id carry no added meaning anywhere.

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 names a specific verb and resource ('Replace a member's whole role list'), which is clearly distinct from the additive sibling add_member_role without naming it. It falls short of a 5 only because it does not explicitly name the sibling it differs from.

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?

There is no when-to-use guidance, no mention of the obvious alternative (add_member_role) versus this wholesale replacement, and no exclusions or prerequisites such as permission or role-hierarchy requirements. The agent must infer usage entirely from the verb.

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