Skip to main content
Glama
TheETR

TheeDiscordMCP

by TheETR

discord_reorder_roles

Bulk reorder Discord roles below the bot's highest role. Use dry run to preview changes before applying.

Instructions

Bulk reorder roles below the bot's highest role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNo
reasonNo
guildIdYes
positionsYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses a single constraint (below the bot's highest role) but omits critical behavioral traits such as the default dryRun behavior (which defaults to true), permission requirements, and what happens on invalid positions. This is insufficient for a mutation tool.

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?

The description is a single front-loaded sentence with no unnecessary words. It conveys the core action and a key constraint efficiently.

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?

Given this is a mutation tool with no annotations, no output schema, and four parameters with zero schema description coverage, the description is far too sparse. It lacks information about dry-run semantics, error handling, and the nature of the response, making the tool difficult to use correctly.

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 0%, so the description must compensate. It does not explain the four parameters (guildId, positions, dryRun, reason) beyond implying that 'positions' relates to role ordering. The phrase 'bulk reorder' provides minimal semantic value, but without explicit clarification, agents cannot reliably construct correct calls.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (bulk reorder), the resource (roles), and a key constraint (below the bot's highest role). It distinguishes from the sibling tool discord_reorder_channels by specifying 'roles' versus channels.

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 implies usage for bulk role reordering but does not provide explicit guidance on when to use this tool versus alternatives like discord_upsert_role or discord_delete_role. The constraint 'below the bot's highest role' hints at a limitation but not alternative recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TheETR/TheeDiscordMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server