better-discord-mcp

by Sys0xdbg

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

discord_create_automod_rule

Create an AutoMod rule to automate moderation in a Discord server. Specify the guild ID and rule configuration.

Instructions

Create an AutoMod rule. rule = raw Discord AutoMod rule object.

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>",
      "rule": "<rule>"
    },
    "name": "discord_create_automod_rule"
  }
}

Input Schema

Name	Required	Description	Default
`rule`	Yes
`guildId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.6/5.0

Behavior2/5

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

The description implies a write operation ('Create') but does not disclose any behavioral traits such as side effects, permission requirements, rate limits, or that the rule object must conform to Discord's API schema. With no annotations, the description carries full burden and falls short.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences) and front-loaded with the purpose. However, its brevity sacrifices essential details, making it too terse for a tool with a complex input. It is concise but incomplete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (nested object parameter, no annotations, no output schema, and many sibling tools), the description is severely inadequate. It fails to provide enough information for an agent to use the tool correctly, such as the structure of the rule object or required fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for parameters. The description only mentions 'rule = raw Discord AutoMod rule object,' which vaguely explains the rule parameter but omits guildId entirely. It adds minimal value beyond the schema, leaving both parameters largely unexplained.

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 'Create an AutoMod rule,' which directly indicates the action and resource. It distinguishes from sibling tools like discord_list_automod_rules, discord_edit_automod_rule, and discord_delete_automod_rule. The mention of 'raw Discord AutoMod rule object' further clarifies the nature of the parameter.

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, nor does it specify prerequisites like required permissions (e.g., Manage Server). It lacks any context about appropriate scenarios or limitations.

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

Deploy Server