discp

create_forum_channel

Creates a new Discord forum channel for community discussions and threads, with options for topic, category, position, and slowmode.

Instructions

Create a new forum channel for community discussions and threads

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": {
      "name": "<name>"
    },
    "name": "create_forum_channel"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Forum channel name
`nsfw`	No	Mark as NSFW
`topic`	No	Guidelines or topic for the forum
`reason`	No	Audit log reason
`guildId`	No	Discord server ID (defaults to DISCORD_GUILD_ID)
`position`	No	Position index
`slowmode`	No	Default slowmode per user (seconds)
`categoryId`	No	Parent category ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 2, 2026

TDQS

C2.9/5.0

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 behavioral burden, yet it discloses nothing beyond the bare action: no permission requirements, no note that a name collision fails, no indication of what the channel's default state is. For a mutation tool with zero annotation coverage this is a real gap.

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, tight sentence with the action front-loaded. Nothing is wasted, though there is also very little substance to waste.

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 an 8-parameter mutation tool with no annotations and no output schema, the description should say more about effects, prerequisites (e.g., Manage Channels permission), and error behavior. What is present is correct but far from complete.

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 100%, so the schema already documents all 8 parameters (name, topic, nsfw, slowmode, position, categoryId, guildId, reason). The description adds no parameter-level detail, which is acceptable given the schema baseline of 3.

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 uses a specific verb+resource ("Create a new forum channel") and scopes it to "community discussions and threads". It is clearly distinguishable from siblings like edit_forum_channel or create_forum_post, though it does not explicitly name an alternative.

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?

No when-to-use or when-not-to-use guidance. The agent is not told how this differs from create_text_channel/create_voice_channel/create_category, or when a forum channel is the right choice over a forum post. Usage must be inferred.

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

Deploy Server