Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

clear_mention_raid_incident

Clears a Discord server's mention raid incident through Auto Moderation, optionally recording an audit log reason, to resolve and document the raid response.

Instructions

Clear Mention Raid Incident. [POST /guilds/{guild_id}/auto-moderation/clear-mention-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": "clear_mention_raid_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.3/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond the endpoint path: it doesn't say what state changes on the server, whether the incident must be active, whether elevated permissions (e.g. manage-guild/MFA) are required, or whether the action is reversible.

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?

Very short and front-loaded with no filler, which is good. But the second half is just a bracketed route string that adds transport trivia rather than agent-relevant meaning, so the brevity reflects under-specification rather than efficiency.

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?

This is a mutation tool with no output schema, and the description does not describe effects, preconditions, or the response. For a moderation action an agent could fire irreversibly, that is a notable gap even though the input schema is fully documented.

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%; both guild_id and reason are documented inline, including that reason appears in the audit log. The description contributes no additional meaning, so the baseline of 3 applies.

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?

The description is essentially the tool name restated ('Clear Mention Raid Incident') plus a raw HTTP route. It never explains what 'clearing' an incident actually does — resolving the flag, allowing @mentions again, deleting the incident record — so an agent must guess the effect from the name alone.

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 guidance on when to use this versus sibling auto-moderation tools like resolve_automod_incident, dismiss_mention, or modify_automod_incident_actions. No prerequisites, no exclusions, no context about when a mention raid incident exists to be cleared.

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