Skip to main content
Glama
wowjinxy
by wowjinxy

create_category

Organize Discord channels by creating new categories to group related channels together, improving server structure and navigation.

Instructions

Create a new channel category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
server_idNo
positionNo
reasonNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler and registration for the MCP tool 'create_category', which creates a new Discord channel category using guild.create_category.
    async def create_category(
        name: str,
        server_id: str | int | None = None,
        position: int | None = None,
        reason: str | None = None,
        ctx: Context = None,
    ) -> str:  # type: ignore[override]
        """Create a new channel category."""
    
        assert ctx is not None
        bot, config = await _acquire(ctx)
        guild_id = _resolve_guild_id(config, server_id)
        guild = await _ensure_guild(bot, guild_id)
    
        kwargs: dict[str, object] = {"name": name}
        if position is not None:
            kwargs["position"] = int(position)
    
        category = await _call_discord(
            "create category",
            guild.create_category(reason=reason, **kwargs),
        )
        return f"Created category {category.name} (ID: {category.id})."
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't specify permission requirements, whether this is reversible (can categories be deleted?), what happens to existing channels, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a basic creation tool and front-loads the essential information (create + resource). Every word earns its place.

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 mutation tool with 4 parameters (0% documented), no annotations, and sibling tools that include other creation operations, this description is incomplete. While an output schema exists (which helps with return values), the description doesn't address permissions, parameter meanings, or usage context. Given the complexity and lack of structured documentation elsewhere, it should do more.

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?

With 0% schema description coverage and 4 parameters (only 'name' required), the description provides no parameter information whatsoever. It doesn't explain what 'server_id', 'position', or 'reason' mean, their expected formats, or how they affect the creation. The description fails to compensate for the complete lack of schema documentation.

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 clearly states the action ('Create') and resource ('new channel category'), making the tool's purpose immediately understandable. It distinguishes itself from siblings like create_text_channel or create_voice_channel by specifying it creates a category rather than a specific channel type. However, it doesn't explicitly contrast with other creation tools beyond the resource name.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing server permissions), when this is appropriate versus creating individual channels directly, or how it relates to siblings like create_text_channel or update_channel. The agent must infer usage from context alone.

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

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