Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Pause invites and DMs

set_incident_actions

Pause new invites and non-friend DMs for up to 24 hours during a raid, lift pauses with confirmation, or report current incident actions and Discord-detected spam.

Instructions

Discord's raid-defense security actions for the whole server. Pause new invites, and pause DMs between members who are not friends, each for up to 24 hours, to lock the server down during a raid. Give a number of hours to pause, 0 to lift a pause, or omit a field to leave it unchanged. Called with neither field, it reports the current state, including any raid or DM spam Discord detected on its own. Pausing, or pausing for longer, happens at once. Lifting a pause that is running, or ending it sooner, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_incident_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dmsNoHours to pause DMs between non-friend members, up to 24. Use 0 to resume, or omit to leave them unchanged.
guildNoGuild (server) name or ID. Omit to use the default guild.
invitesNoHours to pause new invites, up to 24. Use 0 to resume invites, or omit to leave them unchanged.
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token
      Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Addedv1.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, and the description adds substantial context beyond them: the 24-hour cap, that increases apply immediately while reductions require confirmation, and that the first call is a no-op returning a preview plus confirm_token. It also discloses that state reporting includes Discord-detected raid and DM spam.

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?

Four sentences, front-loaded with purpose and scope, then field semantics, then the confirmation protocol. No filler or restated name/title; every sentence carries operational information.

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

Completeness5/5

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

For a 4-parameter mutation tool with no output schema, the description covers what the tool does, when to use it, the confirmation handshake, and what the no-op call returns. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each field, but the description adds real meaning to the two-phase confirm_token workflow (first call changes nothing, second call performs the action) and reiterates the 0/omit semantics in a unified rule. That is a modest but genuine improvement over the schema alone.

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

Purpose5/5

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

The description names a specific verb set and resource scope: 'Pause new invites, and pause DMs between members who are not friends' for the whole server as a raid-defense action. An agent can immediately distinguish this from list_invites or audit_server_security because it clearly mutates server-level raid settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is explicit ('to lock the server down during a raid') and the per-field semantics of 0/omit are spelled out, plus the no-field call reports state. It stops short of naming an alternative sibling for pure inspection (e.g. audit_server_security), so it earns a 4 rather than a 5.

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