Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_scheduled_events

Read-only

Retrieve all scheduled events for a Discord server by guild ID, optionally including attendee counts, to review upcoming activities and manage community scheduling.

Instructions

List Guild Scheduled Events. [GET /guilds/{guild_id}/scheduled-events]

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>"
    },
    "name": "list_guild_scheduled_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
with_user_countNowith user count

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds only the HTTP route mapping and nothing about pagination, whether scheduled events of all statuses are returned, or what 'with_user_count' changes in the payload.

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?

The definition is very short and front-loads the resource being listed. The bracketed REST endpoint is of marginal value to an agent but is not harmful padding, so little is wasted.

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 read-only list tool with full schema coverage and annotations, the bare minimum is present, but the agent still lacks guidance on when to choose this over the user-scoped variant and on how results are returned or filtered.

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 both guild_id and with_user_count are documented in the schema itself, which sets the baseline at 3. The description adds no additional meaning, such as whether with_user_count affects performance or what the counts represent.

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 restates the tool name almost verbatim ('List Guild Scheduled Events') and only adds the underlying REST route. It does signal a guild-scoped list operation, but it does not distinguish this from siblings such as list_user_guild_scheduled_events or get_guild_scheduled_event, so the added value over the name is small.

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 or when-not-to-use guidance, and no mention of the overlapping siblings (list_user_guild_scheduled_events, get_guild_scheduled_event, list_guild_scheduled_event_users). An agent must infer selection criteria entirely from tool names.

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