Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_get_server_stats

Read-only

Retrieve a Discord server snapshot with member counts (humans vs cached bots), channel breakdown, role count, boost tier/count, and creation date.

Instructions

Get a snapshot of server metrics: total members (humans vs cached bots), channel breakdown (text/voice/category), role count, boost tier and count, and creation date. Note: bots are counted from the member cache only, so botsInCache is a lower bound and humans (total minus cached bots) an upper bound. The roles count excludes @everyone. In channels, total covers every channel type, while text, voice and categories count only their own. For the server's owner and description, use discord_get_guild_info.

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

Input Schema

NameRequiredDescriptionDefault
guild_idYesDiscord server (guild) ID (snowflake).

Output Schema

NameRequiredDescriptionDefault
nameYes
rolesYes
humansYes
channelsYes
createdAtYes
boostCountYes
boostLevelYes
botsInCacheYes
totalMembersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "boostCount": {
+      "type": "number"
+    },
+    "boostLevel": {
+      "type": "number"
+    },
+    "botsInCache": {
+      "type": "number"
+    },
+    "channels": {
+      "additionalProperties": false,
+      "properties": {
+        "categories": {
+          "type": "number"
+        },
+        "text": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        },
+        "voice": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total",
+        "text",
+        "voice",
+        "categories"
+      ],
+      "type": "object"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "humans": {
+      "type": "number"
+    },
+    "name": {
+      "type": "string"
+    },
+    "roles": {
+      "type": "number"
+    },
+    "totalMembers": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "name",
+    "totalMembers",
+    "humans",
+    "botsInCache",
+    "channels",
+    "roles",
+    "boostLevel",
+    "boostCount",
+    "createdAt"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / guild_id / description
      Added value: +"Discord server (guild) ID (snowflake)."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing data-quality caveats: bots are counted from the member cache only, making botsInCache a lower bound and humans an upper bound. It also clarifies counting semantics that would otherwise mislead an agent — @everyone excluded from role count, and channel subtype counts not summing to the total channel count.

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

Conciseness5/5

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

Three dense sentences with zero filler: capability first, then the counting caveats, then the sibling redirect. Front-loaded and logically ordered, with no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need no prose, yet the description still explains how to interpret the trickiest fields (bounds on bots/humans, channel totals). Combined with annotations covering the safety profile, nothing an agent needs to call and interpret this correctly is missing.

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 coverage is 100% and the single guild_id parameter is fully documented with a snowflake pattern in the schema, so the description adds nothing about parameters and needs not. Baseline 3 applies since the schema carries the semantics.

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

Purpose5/5

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

Opens with a specific verb+resource ("Get a snapshot of server metrics") and enumerates exactly what is returned: member counts split humans/cached bots, channel breakdown by text/voice/category, role count, boost tier and count, creation date. It also names a sibling (discord_get_guild_info) and the fields that belong to it, so an agent can separate the two without opening either schema.

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?

Explicitly routes the agent elsewhere for the server's owner and description via discord_get_guild_info, which is a real alternative-selection rule. It stops short of a full when/when-not statement (e.g., vs discord_list_members for exact member counts), but the practical usage context is clear.

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