Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_scheduled_event

Read-only

Retrieve details of a Discord guild scheduled event by guild ID and event ID, with an option to include the user count for attendance tracking.

Instructions

Get Guild Scheduled Event. [GET /guilds/{guild_id}/scheduled-events/{event_id}]

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": "get_guild_scheduled_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesScheduled event ID
guild_idYesServer (guild) ID
with_user_countNowith user count

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 the safety profile is covered. The description adds nothing beyond the endpoint path — no note on error behavior for missing/invalid event IDs, no indication of what the call returns, and no explanation of how with_user_count changes the response.

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 fragments with no filler and the resource identified up front. The bracketed HTTP route is marginally redundant with the tool name but does orient an agent familiar with the underlying API.

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 read tool with no output schema, so the description carries the burden of telling the agent what comes back — and it says nothing about return shape or the effect of with_user_count. For a single-resource fetch with three parameters and undefined return values, that is a meaningful gap.

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 three parameters are already documented in the schema, including the terse but present "with user count" flag. The description contributes no additional meaning beyond the schema, which is the baseline expectation when coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially the tool name restated ("Get Guild Scheduled Event") plus a raw HTTP path. It does identify a specific resource and implies a single-item retrieval versus the sibling list_guild_scheduled_events, but the distinction is left entirely to inference from the name 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 when to prefer get_guild_scheduled_event versus list_guild_scheduled_events, list_user_guild_scheduled_events, or get_guild_scheduled_event_user_count. An agent must guess from names 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