Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_channel_position

Moves a Discord channel to a specified position within its category to reorder and organize channels.

Instructions

Move a channel to a position inside its category.

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>",
      "channelId": "<channelId>",
      "position": "<position>"
    },
    "name": "discord_set_channel_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildIdYesDiscord id (snowflake)
positionYes
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It does not say that this is a mutating operation, what permissions are required, whether sibling channels get shifted, or whether the change is reversible; only the vague phrase "inside its category" hints at scope.

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, so it is efficiently structured. It is terse to the point of under-specification, but no wording is wasted.

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 three-required-parameter mutation tool with no annotations, no output schema, and only partial schema descriptions, this one sentence is not enough. An agent calling it correctly needs permission requirements, side effects on other channels, and confirmation of what a valid position means at the boundaries.

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 description coverage is only 33%: guildId is described as a snowflake, channelId is an undescribed $ref to guildId, and position has bounds but no description. The phrase "inside its category" does add real meaning by implying position is interpreted relative to the category rather than the whole guild, which is more than the schema says, but the two id parameters get no additional explanation.

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 pairs a specific verb ("Move") with a specific resource ("a channel") and states the resulting state ("to a position inside its category"). That is far clearer than a bare name restatement, though it never distinguishes itself from neighboring tools like discord_edit_channel or discord_set_role_position.

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 guidance on when to use this instead of discord_edit_channel, no mention of prerequisites such as needing Manage Channels, and no stated constraints (e.g. whether the channel must already belong to a category). The agent must infer all routing and preconditions.

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