Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

mark_interested_in_event

Marks your Discord account as interested in a scheduled server event using its guild ID and event ID, so you can register interest without manual navigation.

Instructions

Mark yourself as interested in an event. [PUT /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": "mark_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

B3.2/5.0
Behavior3/5

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

Annotations already declare the non-read-only, non-destructive, open-world profile; the description adds the concrete PUT endpoint and the fact that the target is the calling user ('yourself', '@me'), which is useful context. It omits what happens on repeat invocation (already-interested case), error conditions, and required scopes.

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?

One short sentence with the action front-loaded, plus a bracketed route reference. Nothing is wasted, though the endpoint bracket is marginally redundant for an agent that never needs the raw HTTP path.

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 simple two-required-parameter mutation with no output schema and full schema coverage, the core information is present. It still leaves out idempotency behavior and the relationship to the unmark and occurrence siblings, which an agent needs to choose 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 description coverage is 100%, so guild_id and event_id are already documented. The endpoint path implicitly maps the parameters to guild and event, but the description contributes no syntax, format, or constraint details beyond the schema – baseline 3 applies.

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?

States a specific verb and resource: 'Mark yourself as interested in an event', which unambiguously identifies the write action. It does not name the counter-operation (unmark_interested_in_event) or the occurrence variant, so sibling differentiation comes only from the tool name.

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, when-not-to-use, or prerequisite guidance is given. An agent must infer that unmark_interested_in_event is the inverse and that mark_interested_in_event_occurrence handles sub-events, with nothing in the description to confirm that routing.

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