Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_role_position

Moves a Discord role to a specific position within a guild to reorder the role hierarchy. Requires Manage Roles.

Instructions

Move a role to a position. 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>",
      "position": "<position>"
    },
    "name": "discord_set_role_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleIdYes
guildIdYesDiscord id (snowflake)
positionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the Manage Roles auth requirement, which is genuinely useful, but it omits mutation consequences such as how other roles shift, whether the role hierarchy of the bot limits the move, and reversibility.

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?

Two short sentences with the operation front-loaded and the prerequisite second; nothing is wasted. It is arguably too terse, but there is no filler or redundancy.

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 three-parameter mutation with no annotations and no output schema, the definition is minimally adequate: it names the action and the required permission. It leaves out positional semantics and reordering side effects that an agent would need to call it 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 33%: only guildId is annotated (as a snowflake), while roleId relies on a $ref and position has no description beyond bounds 0-1000. The description says 'move to a position' but does not explain indexing, whether 0 is top or bottom, or hierarchy constraints, so it fails to compensate for the coverage gap.

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 gives a specific verb and resource ('Move a role to a position'), so the agent knows exactly what operation is performed. It does not distinguish itself from near siblings such as discord_set_channel_position or discord_edit_role, but the operation itself is unambiguous.

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?

'Requires Manage Roles' is a useful permission prerequisite that tells the agent when the call will succeed. There is no guidance on when to use this versus discord_edit_role or discord_set_channel_position, so usage context is only implied.

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