Skip to main content
Glama

discord_get_server_stats

Retrieve Discord server statistics including member counts, channel details, roles, and boost level to monitor community growth and structure.

Instructions

Get server statistics: member count (humans vs bots), channels, roles, boost level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes

Implementation Reference

  • The logic for handling the discord_get_server_stats tool, which fetches guild data and compiles statistics.
    case "discord_get_server_stats": {
      const guild = await (await discord.guilds.fetch(validateId(args.guild_id, "guild_id"))).fetch();
      await guild.channels.fetch();
      const cachedBots = guild.members.cache.filter((m) => m.user.bot).size;
      return {
        content: [{
          type: "text", text: JSON.stringify({
            name: guild.name, totalMembers: guild.memberCount,
            humans: guild.memberCount - cachedBots, botsInCache: cachedBots,
            channels: {
              total: guild.channels.cache.size,
              text: guild.channels.cache.filter((c) => c.type === ChannelType.GuildText).size,
              voice: guild.channels.cache.filter((c) => c.type === ChannelType.GuildVoice).size,
              categories: guild.channels.cache.filter((c) => c.type === ChannelType.GuildCategory).size,
            },
            roles: guild.roles.cache.size - 1,
            boostLevel: guild.premiumTier, boostCount: guild.premiumSubscriptionCount ?? 0,
            createdAt: guild.createdAt.toISOString(),
          }, null, 2),
        }],
      };
    }
  • The MCP tool definition for discord_get_server_stats, including the input schema.
    {
      name: "discord_get_server_stats",
      description: "Get server statistics: member count (humans vs bots), channels, roles, boost level.",
      inputSchema: {
        type: "object",
        properties: { guild_id: { type: "string" } },
        required: ["guild_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what data is returned but doesn't mention permissions required, rate limits, whether it's a read-only operation, error conditions, or response format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that immediately states the tool's purpose and enumerates the specific statistics returned. Every word earns its place with zero wasted text, making it easy to parse quickly.

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?

Given no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It specifies what data is returned but doesn't cover behavioral aspects (permissions, rate limits), parameter context, or how to interpret results. For a tool in a complex Discord API environment with many sibling tools, more context would be helpful.

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?

The description doesn't mention any parameters, while the schema has 1 parameter with 0% description coverage. Since schema_description_coverage is 0%, the description should compensate but doesn't. The baseline is 3 because the single parameter 'guild_id' is self-explanatory for Discord context, but no additional semantic context is provided.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get server statistics' with specific metrics listed (member count breakdown, channels, roles, boost level). It uses a specific verb ('Get') and resource ('server statistics'), but doesn't explicitly differentiate from sibling tools like 'discord_get_guild_info' which might provide overlapping information.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or compare it to similar sibling tools like 'discord_get_guild_info' or 'discord_list_channels' that might provide related data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server