Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

unmark_interested_in_event_occurrence

Destructive

Removes your interest from a specific occurrence of a recurring Discord scheduled event, so you are no longer marked as interested in that exception.

Instructions

Delete Guild Scheduled Event Exception User. [DELETE /guilds/{guild_id}/scheduled-events/{event_id}/{exception_id}/users/@me]

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": "unmark_interested_in_event_occurrence"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is covered. The description does add one piece of non-annotation context: the /users/@me path shows the operation only removes the authenticated user's own interest, not other users'. It does not state irreversibility or what happens if the occurrence does not exist.

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

Conciseness4/5

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

Two compact elements with no filler: the operation name followed by the endpoint. It is front-loaded, though brevity here reflects under-specification rather than disciplined editing.

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 destructive three-ID operation with no output schema, the description never explains the event/exception relationship, what state the caller ends up in, or error behavior when the exception or interest does not exist. It relies almost entirely on annotation hints and naming convention to be callable correctly.

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 coverage is 100% with all three required IDs individually documented, so the schema carries the parameter burden. The description adds nothing about how event_id relates to exception_id or what an "exception user" record is, so 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 gives a verb and resource ("Delete Guild Scheduled Event Exception User") plus the raw HTTP route, so the operation is identifiable. However, it uses internal API phrasing rather than the user-facing concept implied by the tool name (removing your interest in a single occurrence of a recurring event), and the /users/@me segment is the only hint that this targets the calling user. An agent must decode jargon to distinguish it from delete_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?

No when-to-use guidance, no prerequisites, and no reference to the inverse sibling mark_interested_in_event_occurrence or to delete_guild_scheduled_event_exception. The agent must infer the distinction from naming conventions alone.

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