Skip to main content
Glama
iprashantraj

mcp-discord-bridge

move_channel

Move a Discord channel to a different category or remove it from its current category.

Instructions

Move a channel into a different category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
category_idNoTarget category ID — omit or leave empty to remove from category
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Move a channel into a different category', failing to mention that omitting category_id removes the channel from a category (though this is noted in the parameter description), and does not cover permissions, side effects, or return values.

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?

The description is a single, front-loaded sentence with no wasted words. However, it could be slightly more informative by including the removal option, but overall it is concise.

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 simple mutation tool with two parameters and no output schema, the description conveys the primary action but misses important behavioral details like the removal capability and permission requirements. It is minimally adequate.

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 50% (only category_id has a description), and the tool description does not add any parameter information. It fails to describe channel_id or clarify how parameters relate to the action, leaving the agent with incomplete guidance.

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 uses a specific verb ('Move') and resource ('channel into a different category'), clearly distinguishing it from other channel operations like create, delete, or rename.

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 states when to use the tool (to move a channel to a different category) but does not mention when not to use it or provide alternatives, nor does it indicate necessary permissions or prerequisites.

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/iprashantraj/mcp-discord-bridge'

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