Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

validate_guild_automod_rule

Validate a Discord server's AutoMod rule configuration before applying it. Checks trigger metadata against the guild to catch invalid rules early.

Instructions

Validate Guild AutoMod Rule. [POST /guilds/{guild_id}/auto-moderation/rules/validate]

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": {
      "guild_id": "<guild_id>",
      "trigger_metadata": "<trigger_metadata>"
    },
    "name": "validate_guild_automod_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
trigger_metadataYestrigger metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds only a raw POST path and never clarifies whether validation persists anything, what it checks, what permissions are required, or how failures are surfaced — meaningful gaps for a tool whose entire purpose is producing a validation verdict.

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?

Two short, front-loaded fragments with no filler — the action is stated first and the endpoint second. The bracketed HTTP path is largely redundant for an agent and consumes half the available text, which is the only 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?

With no output schema and no annotations indicating a dry-run semantic, the description should explain what a validation response means and whether any state changes. It supplies none of this, and the readOnlyHint=false annotation alongside a "validate" endpoint is left unexplained, which is exactly the ambiguity the description needed to resolve.

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 guild_id and reason are already documented; baseline 3 applies. The one genuinely opaque parameter, trigger_metadata, is an open nested object whose internal shape is left undefined by both schema and description, so no additional meaning is contributed.

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 gives a specific verb and resource ("Validate Guild AutoMod Rule") plus the underlying endpoint, which distinguishes it from the create/modify/delete/get siblings in the AutoMod family. It stops short of explaining what "validate" actually means, but the action is identifiable without opening the schema.

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?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives such as create_guild_automod_rule or modify_guild_automod_rule. The only cue that this is a pre-flight check rather than a persisted change comes from the word "validate" in the name.

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

Deploy Server

Other Tools