Skip to main content
Glama

Scheduled events (admin)

discord_admin_events
Destructive

Manage scheduled Discord events by listing, creating, editing, cancelling, or deleting voice/stage and external-location events with ISO 8601 start/end times.

Instructions

List, create, edit, cancel or delete scheduled events. An event is in a voice channel (channel_id) or somewhere else (location; needs an end time). Times are ISO 8601.

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": {
      "action": "<action>"
    },
    "name": "discord_admin_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
nameNo
startNoISO 8601, e.g. 2026-11-20T15:00:00+05:30
actionYes
reasonNoReason, recorded in Discord's audit log
event_idNoedit/cancel/delete: the event
locationNoFor events outside Discord (Meet link, office address)
channel_idNoVoice or stage channel for the event
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the destructive profile is covered. The description adds the non-obvious constraint that location-based events require an end time and that times are ISO 8601, but it does not explain the semantic difference between cancel and delete, whether edits are reversible, or permission requirements.

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?

Three short sentences, front-loaded with the operation list and followed by the two constraints that actually change how the tool is called. No filler or restatement of the title.

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

Completeness3/5

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

For a nine-parameter destructive tool with no output schema, the definition covers the key branching constraint but omits per-action parameter requirements, permission needs, and what list/cancel return. Adequate to call correctly in common cases, but an agent would still have to infer requirements for edit and cancel from the schema.

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 description coverage is 56%, and the description compensates for a real gap: the channel_id/location mutual exclusivity and the conditional need for `end` are not expressed anywhere in the schema. It also reinforces the ISO 8601 format for start. It leaves name, description and the cancel/delete distinction to the schema alone, so it is not fully compensating.

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

Purpose4/5

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

The description names a specific resource (scheduled events) and enumerates all five operations (list, create, edit, cancel, delete), so an agent knows exactly what it is buying. It does not explicitly distinguish itself from siblings such as discord_admin_create_channel or discord_activity_report, but the resource scope is distinctive enough that confusion is unlikely.

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

Usage Guidelines3/5

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

It provides one real conditional rule: an event is either in a voice channel via channel_id or elsewhere via location, and location events need an end time. That is useful branch guidance, but there is no statement of prerequisites (e.g. Manage Events permission), no per-action requirements (which fields create vs edit need), and no notion of when to prefer cancel over delete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.