Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_scheduled_event_exception

Creates an exception for a Discord scheduled event occurrence, adjusting or canceling its start, end, or original time.

Instructions

Create Guild Scheduled Event Exception. [POST /guilds/{guild_id}/scheduled-events/{event_id}/exceptions]

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

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
event_idYesScheduled event ID
guild_idYesServer (guild) ID
is_canceledNo
scheduled_end_timeNo
scheduled_start_timeNo
original_scheduled_start_timeYesoriginal scheduled start time (ISO8601 time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write nature and openness are covered by structured data. The description adds nothing beyond that: it does not explain what gets created, whether it affects an existing recurring event, whether required fields must match the parent event, or what errors occur on conflicts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but that shortness reflects under-specification rather than efficiency: one sentence repeats the title and one bracket holds route metadata. No informative content is front-loaded because there is no informative content.

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

Completeness1/5

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

This is a seven-parameter mutation with a 57% documented schema and no output schema, which demands more descriptive support than average. The definition provides none, leaving an agent unable to determine semantics of the required time field or the relationship between the exception and its parent event.

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

Parameters2/5

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

Schema coverage is only 57%, and the description supplies no parameter meaning whatsoever. It does not clarify the required original_scheduled_start_time (presumably identifying which occurrence is being excepted) or how is_canceled, scheduled_start_time, and scheduled_end_time interact, so the undocumented portion of the schema is left unexplained.

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 restates the tool name ("Create Guild Scheduled Event Exception") and appends the HTTP route, which is a tautology rather than an explanation. It never says what an "exception" actually is in this domain (an override of a single occurrence of a recurring scheduled event), so an agent cannot infer the effect from the text 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 when-to-use guidance at all: no statement of prerequisites, no mention of when to prefer this over modify_guild_scheduled_event_exception or create_guild_scheduled_event, and no distinction from the delete/list exception siblings. Only the bare endpoint is provided.

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