Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_scheduled_event_user_count

Read-only

Returns the number of users interested in a guild's scheduled event, optionally filtered by exception IDs. Use guild_id and event_id to retrieve attendance counts for planning.

Instructions

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

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_user_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesScheduled event ID
guild_idYesServer (guild) ID
guild_scheduled_event_exception_idsNoguild scheduled event exception ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds no behavioral context beyond that — no rate-limit notes, no mention of what the count reflects (interested vs. subscribed users), and no indication of pagination or scoping.

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?

The definition is very short and front-loaded with the resource name, then the endpoint. There is no wasted wording, but the brevity comes from under-specification rather than tight writing — the second sentence is a raw route string that adds only marginal interpretive value.

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?

This is a simple read-only count tool with three fully documented parameters and no output schema, so the burden is light. Still, the description does not confirm the return shape (a count object) or clarify which population is counted, which would have made it complete for an agent deciding between this and the users-listing sibling.

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%, with guild_id, event_id and guild_scheduled_event_exception_ids all documented in the schema itself, so the baseline of 3 applies. The description contributes nothing about parameter meaning or how exception IDs affect the count, leaving the schema to do all the work.

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 names the resource (Guild Scheduled Event User Count) and adds the concrete REST route GET /guilds/{guild_id}/scheduled-events/{event_id}/users/counts, which does confirm this returns a count of users rather than the user list. However, the prose portion is essentially a restatement of the tool name, so the only real disambiguation comes from the endpoint path.

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 guidance on when to use this versus siblings such as list_guild_scheduled_event_users or get_guild_scheduled_event. The agent must infer from the name that this returns an aggregate count rather than the roster, and nothing states prerequisites, exclusions, or alternatives.

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