Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_scheduled_event_exception

Destructive

Remove a specific exception from a recurring Discord scheduled event. Use it to delete an exception entry by guild, event, and exception ID, optionally logging a reason in the audit log.

Instructions

Delete Guild Scheduled Event Exception. [DELETE /guilds/{guild_id}/scheduled-events/{event_id}/exceptions/{exception_id}]

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>",
      "event_id": "<event_id>",
      "exception_id": "<exception_id>"
    },
    "name": "delete_guild_scheduled_event_exception"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
event_idYesScheduled event ID
guild_idYesServer (guild) ID
exception_idYesRecurring event exception 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 destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that and the route: it does not say whether deletion is permanent, what happens to the recurring schedule, what permissions are required, or how the reason field surfaces 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?

The description is short and front-loaded, with no filler prose. However, the first sentence merely repeats the title, and the bracketed route duplicates structured information without adding decision-relevant content.

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 destructive mutation with three required identifiers, yet the description says nothing about irreversibility, required permissions, or effects on the recurrence. The fully covered schema and the annotations mitigate this, but for a destructive tool the description is too thin.

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 all four parameters including guild_id, event_id, exception_id, and reason are already documented in the schema. The description provides no additional meaning such as ID formats or the relationship among the three identifiers, so the baseline 3 applies.

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 names a specific verb and resource (delete a guild scheduled event exception) and the HTTP route, so the operation is identifiable. But the first sentence is essentially the tool name restated, and it offers no differentiation from closely related siblings such as delete_guild_scheduled_event or modify_guild_scheduled_event_exception.

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 tool, no prerequisite conditions, and no mention of alternatives or when not to use it. The only cue is the endpoint path, which implies a single-exception deletion but not the circumstances that call for it.

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