Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

report_automod_incident

Reports a Discord AutoMod raid incident to the server’s audit log, letting moderators document the event with an optional reason for later review.

Instructions

Report AutoMod Incident. [POST /guilds/{guild_id}/auto-moderation/report-raid]

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the description repeats rather than extends that by echoing a POST endpoint. It says nothing about what reporting actually triggers (raid mode, alert actions, audit-log entries), whether it is idempotent or rate limited, or what permission level is required for a state-changing, open-world call.

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?

It is short and front-loaded, but the brevity comes from omission rather than discipline: one clause repeats the title and the other is a technical endpoint string of little use to an agent choosing a tool.

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

Completeness3/5

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

The schema is fully described and annotations carry the safety profile, so the structural fields are adequate for a 2-parameter tool with no output schema. What is missing is the semantic payload — what a "report" does to the guild and how it interacts with the resolve/clear incident tools — which for a state-changing, open-world action leaves a real gap.

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%, with guild_id ("Server (guild) ID") and reason ("Reason (shown in the audit log)") both documented in the schema, so the baseline is 3. The description adds no extra meaning — it does not say what the reason is attached to or whether guild_id must be a guild the caller administers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Report AutoMod Incident" restates the tool name rather than explaining the action, and the only added information is the raw endpoint path "[POST /guilds/{guild_id}/auto-moderation/report-raid]". The word "raid" in the path hints that this reports a raid to Discord's AutoMod, but the prose never says so, and nothing distinguishes it from resolve_automod_incident or clear_mention_raid_incident.

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 (e.g. required permissions or AutoMod being enabled), and no mention of the sibling tools that handle the adjacent resolve/clear operations. The agent must infer context entirely from 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