Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get event attendees

get_event_attendees
Read-only

Retrieve the members who marked themselves interested in a Discord event, using the event name or ID and an optional guild and limit.

Instructions

Members who marked themselves interested in an event.

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": {
      "event": "<event>"
    },
    "name": "get_event_attendees"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYesEvent name or ID.
guildNoGuild (server) name or ID. Omit to use the default guild.
limitNoMax entries. Default 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

C2.7/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, so the description's burden is lighter. It contributes the semantic detail that membership is self-declared interest rather than confirmed attendance, which matters. It says nothing about ordering, pagination behavior beyond the limit parameter, or result size, so it adds only moderate value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment, so there is no wasted wording, but the brevity comes from under-specification rather than tight editing. There is no front-loaded verb to anchor the agent's reading.

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?

For a three-parameter list tool with no output schema, the description should at least indicate what is returned per attendee or how results are bounded. It omits return shape, pagination behavior, and any error case such as an unknown event, leaving the agent to discover these by calling.

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 (event, guild, limit with its 1-100 range and default of 25) are already documented. The description adds no additional meaning about how event name resolution works, what omitting guild does in practice, or how limit interacts with paging.

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 is a noun phrase rather than a verb+resource statement, effectively restating the title 'Get event attendees' with one added nuance: attendees are members who marked themselves 'interested' rather than confirmed registrants. That nuance is genuinely useful, but it does not distinguish this tool from nearby siblings such as get_event or list_event_subscriptions.

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 prerequisites, and no mention of alternatives. An agent must infer from the name alone that this is the read path for attendee lists, and nothing tells it whether get_event or list_event_subscriptions should be preferred for overlapping needs.

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