discp

create_automod_rule

Create Discord AutoModeration rules to block bad words, spam, or mention raids. Define triggers, keywords, alert channels, and timeout actions.

Instructions

Create a new AutoModeration rule (e.g. block bad words, spam, or mention raids)

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_automod_rule"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Rule name
`reason`	No	Audit log reason
`guildId`	No	Discord server ID (defaults to DISCORD_GUILD_ID)
`keywordsCsv`	No	Comma-separated list of keywords to match (for KEYWORD trigger)
`triggerType`	No	Rule trigger type	KEYWORD
`blockMessage`	No	Whether to block the triggering message
`mentionLimit`	No	Max allowed unique mentions (for MENTION_SPAM trigger)
`alertChannelId`	No	Channel ID to send an alert log message to
`timeoutSeconds`	No	Timeout user for N seconds (up to 28 days)
`regexPatternsCsv`	No	Comma-separated list of regex patterns

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 burden. It implies a mutation but discloses nothing about permission requirements, that the rule takes effect immediately, or any rate limits. The examples are the only added behavioral hint.

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?

A single front-loaded sentence with no wasted words; the verb and resource come first and the examples are a tight parenthetical.

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 10-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits the important relationship that triggerType determines which params apply (keywordsCsv for KEYWORD, mentionLimit for MENTION_SPAM), leaving the agent to infer conditional parameter usage from schema text alone.

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 ten parameters, including defaults and enum values. The description's examples of triggers loosely map to the triggerType enum but add no syntax or format detail beyond the schema.

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?

States a specific verb (create) and resource (AutoModeration rule) and gives concrete examples of trigger categories. It is distinguishable from edit_automod_rule, delete_automod_rule, and list_automod_rules, though it never names those siblings explicitly.

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 guidance on when to create a rule versus edit an existing one, no mention of required bot permissions (Manage Server), and no note that it needs a guild context. Usage is only implied by the verb.

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

Deploy Server