Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_add_role

Assign one or more roles to a Discord member using guild, user, and role IDs; requires Manage Roles and a role below the account's highest role.

Instructions

Add one or more roles to a member. Requires Manage Roles and a role below the account highest role.

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_add_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)
roleIdsYes

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 provided, the description must carry the full behavioral burden. It does disclose the key authorization requirement and hierarchy constraint, which is genuinely valuable, but omits mutation semantics such as idempotency when a role is already assigned, error behavior, and whether the operation is reversible.

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 sentences, front-loaded with the action, and zero wasted wording. The permission constraint follows immediately after the core purpose.

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 4-parameter mutation tool with no annotations and no output schema, the definition covers permissions and role hierarchy but not the audit-log reason parameter, duplicate-role behavior, or expected response. Adequate but with clear gaps.

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%, so the description needs to compensate. It maps 'one or more roles' to the roleIds array (consistent with minItems/maxItems) and 'a member' to userId, but leaves the reason parameter undocumented and does not explain guildId beyond the schema's pattern description.

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?

States a specific verb (add) and resource (roles) applied to a member, which is directly distinguishable from the discord_remove_role sibling. It stops short of naming alternatives or clarifying its relationship to role creation/editing tools, keeping it at 4 rather than 5.

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?

Provides prerequisite conditions (Manage Roles permission and role hierarchy placement), which is useful context for attempting the call. However, it offers no explicit when-to-use guidance versus alternatives like discord_edit_role or discord_remove_role, leaving selection logic implicit.

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