Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_scheduled_event_exception

Change a recurring guild scheduled event exception’s start/end time or cancellation status for a specific server and event, with an optional audit log reason.

Instructions

Modify Guild Scheduled Event Exception. [PATCH /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": "modify_guild_scheduled_event_exception"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
event_idYesScheduled event ID
guild_idYesServer (guild) ID
is_canceledNo
exception_idYesRecurring event exception ID
scheduled_end_timeNo
scheduled_start_timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 safety is largely covered. The description adds only the HTTP route, which implies a PATCH-style partial update but does not say what happens to omitted fields, what permissions are needed, or what the response contains.

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, so there is no wasted prose, but the second half is a raw endpoint path that carries little decision value for an agent. Brevity here reflects under-specification rather than disciplined concision.

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?

For a mutation tool with 7 parameters, 3 required IDs, and no output schema, the definition leaves the agent without any behavioral or conditional detail. The annotations cover the safety profile, but the mutation semantics and partial-update behavior remain undocumented.

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 description coverage is only 57%, and the description contributes nothing about any of the 7 parameters. A caller gets no explanation of how is_canceled interacts with the time fields or why scheduled_end_time is conditionally required, beyond the terse schema notes.

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 verb-and-resource pair ('Modify Guild Scheduled Event Exception'), but it is essentially a restatement of the tool name with no scope or effect described. It does not distinguish this tool from sibling 'modify_guild_scheduled_event' or 'create/delete_guild_scheduled_event_exception' beyond the word '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?

No when-to-use guidance is given: nothing states that this is a partial update of an existing exception, when an exception should be created instead, or what prerequisites (permissions, existing event) apply. The only contextual hint is the REST path.

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