Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

resolve_automod_incident

Resolves a Discord AutoMod incident as a false alarm by submitting the alert message ID, guild ID, and audit-log reason. Use it to clear incorrect moderation flags for a server.

Instructions

Resolve AutoMod Incident. [POST /guilds/{guild_id}/auto-moderation/false-alarm]

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>",
      "alert_message_id": "<alert_message_id>",
      "reason": "<reason>"
    },
    "name": "resolve_automod_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesReason (shown in the audit log)
guild_idYesServer (guild) ID
alert_message_idYesalert message id (ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond the route: it does not say what resolving does to the alert message (dismiss, delete, mark resolved), whether it is reversible, or that the reason appears in the audit log.

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 with no filler, but the single substantive sentence is a restated title and the endpoint path, so little content is being conveyed concisely. Nothing is wasted, but little is earned.

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 three-required-parameter mutation with no output schema, so the description carries the burden of explaining effect and preconditions. It omits what state change occurs, what happens if the alert ID is invalid or already resolved, and what the response contains.

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, alert_message_id and reason are already documented in the schema. The description adds no meaning beyond that, which is the baseline expectation when the schema does the work.

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

Purpose3/5

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

The description gives a verb+resource (resolve an AutoMod incident) plus the HTTP route, so the general action is identifiable. However, 'resolve' is not defined, and it does not distinguish itself from siblings such as modify_automod_incident_actions or execute_automod_alert_action, so an agent cannot tell precisely what resolving does versus those.

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 named alternative. The agent must infer from the raw endpoint that this is the false-alarm dismissal path, with no statement of when that is appropriate versus the other AutoMod tools.

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