Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

unmark_interested_in_event

Destructive

Removes your interest from a Discord scheduled event using the guild and event ID, so you no longer appear as interested.

Instructions

Remove your interest in an event. [DELETE /guilds/{guild_id}/scheduled-events/{event_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>"
    },
    "name": "unmark_interested_in_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesScheduled event ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 real value via the endpoint path — the "users/@me" segment shows it only removes the caller's own interest, not other members' — but it omits whether a repeat call errors or is a no-op.

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 short sentences with the action stated first and the endpoint appended as clarifying detail. Nothing is padded, though the bracketed route is the least agent-relevant element.

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

Completeness4/5

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

For a two-parameter, schema-fully-documented delete whose safety traits are already in annotations, the description covers enough to call it correctly. Missing return/error behavior is a minor gap since no output schema exists.

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%, with both guild_id and event_id documented in the schema itself, so a baseline of 3 applies. The endpoint path reinforces that event_id is a scheduled event under a guild, but no additional parameter semantics are introduced.

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?

"Remove your interest in an event" names a specific verb (remove interest) and resource (scheduled event), which is clearly the inverse of mark_interested_in_event. It stops short of naming the counterpart tool explicitly, but the write is unambiguous.

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?

Usage is only implied: an agent can infer it should call this when the user no longer wants to be marked interested. There is no explicit when-to-use framing, no mention of the *_occurrence variant, and no note about what happens if the user was never interested.

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