Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

mark_interested_in_event_occurrence

Marks the current Discord user as interested in a specific occurrence of a recurring guild scheduled event using guild, event, and exception IDs.

Instructions

Create Guild Scheduled Event Exception User. [PUT /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>",
      "response": "<response>"
    },
    "name": "mark_interested_in_event_occurrence"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesScheduled event ID
guild_idYesServer (guild) ID
responseYesresponse
exception_idYesRecurring event exception ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 description need only add context such as idempotency (PUT implies repeated calls are safe), auth requirements, or the effect on event interest counts. Instead it repeats the endpoint path with no behavioral detail, leaving an agent without confirmation of what state changes occur.

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 sentences with no filler, and the resource action is front-loaded. The endpoint bracket adds locational context at low cost, though the phrasing is jargon-heavy rather than agent-friendly.

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?

This is a four-parameter mutation tool with no output schema and only minimal annotations. The definition omits what 'interest' means here, whether the call is idempotent, what a 'recurring event exception' is, and what the response parameter controls, so an agent cannot confidently invoke it without external knowledge.

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%, so all four parameters are documented in the schema, and the baseline of 3 applies. The description adds only the URL template showing where the IDs are placed, which is mildly useful but does not clarify semantics such as valid values for 'response' (typed number with the placeholder description 'response').

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 the resource via Discord API jargon ('Guild Scheduled Event Exception User') and gives the endpoint path, from which an agent can infer a PUT that associates the current user with an event exception. However, it never states in plain terms that this marks the caller as interested in one occurrence of a recurring event, nor does it distinguish that meaning from the sibling mark_interested_in_event. The purpose is inferable rather than stated.

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, no mention of the unmark_interested_in_event_occurrence counterpart for reversal, and no note about how this differs from mark_interested_in_event (whole event) or the exception-management siblings. The agent must infer selection from the tool name 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