Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_events

Read-only

Retrieve recent Discord events such as messages, reactions, friend requests, calls, and joins; use since_seq to poll for only new events.

Instructions

Recent live events received since connecting (new/edited/deleted messages, reactions, friend requests, calls, joins…). Use since_seq to poll for only new ones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50
typesNoe.g. ["MESSAGE_CREATE","MESSAGE_REACTION_ADD","RELATIONSHIP_ADD","CALL_CREATE"]
guild_idNoUse "@me" for DMs only
since_seqNo
channel_idNo
exclude_mineNoSkip your own messages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds non-obvious behavior: the buffer only accumulates events from the moment of connection and can be polled incrementally via since_seq. It doesn't state whether the buffer evicts old events, how limit truncation interacts with since_seq, or what happens on reconnect, which are meaningful gaps for a polling tool.

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 the core purpose front-loaded and the polling instruction second. The parenthetical event enumeration is slightly loose but does useful work by hinting at the event universe; nothing is redundant with the schema.

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?

With no output schema, the description should convey something about the shape of a returned event (fields, ordering, sequence numbering), and it doesn't. The buffer semantics and polling hint are valuable, but for a 6-parameter tool with two undocumented params and no return-value description, the definition is only adequate.

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 67%, so several parameters are already documented (limit default 50, types examples, guild_id '@me' for DMs, exclude_mine). The description adds real meaning for since_seq, explaining its polling purpose, but leaves channel_id undocumented and doesn't clarify how types interacts with filter semantics. This matches the baseline of 3 with modest added value.

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 and scope ('Recent live events received since connecting') and enumerates concrete event categories (messages, reactions, friend requests, calls, joins), so an agent knows this is an inbound event buffer rather than a scheduled-events listing. It stops short of explicitly contrasting with similar siblings, which keeps it from a 5.

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

Usage Guidelines4/5

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

It gives a concrete usage pattern: use since_seq to poll for only new events, which tells the agent how to use the tool in a loop and implies the initial call omits it. There are no explicit when-not conditions or named alternatives, so it falls short of a 5.

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