Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_role_member_counts

Read-only

Retrieves member counts for every role in a Discord guild by guild ID, helping you audit role distribution and spot unassigned or overloaded roles.

Instructions

Member count of every role. [GET /guilds/{guild_id}/roles/member-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>"
    },
    "name": "get_guild_role_member_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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. The description adds only the REST endpoint path, and says nothing about whether bot members are included, whether empty roles appear, or what permission scope the call requires.

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?

One short fragment plus an endpoint tag, front-loaded with the essential fact and free of padding. It is arguably under-specified rather than verbose, which the completeness dimension captures.

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?

For a simple single-parameter read with full schema coverage and no output schema, the definition is minimally sufficient to invoke the tool correctly. It stops short of describing the response shape (a role-to-count mapping), which is the main missing piece for an agent consuming the result.

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?

Only one parameter (guild_id) and the schema already documents it at 100% coverage with the description 'Server (guild) ID'. The description adds no further meaning, so the baseline of 3 applies.

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?

States the resource and the returned metric precisely: member counts aggregated across every role in a guild. It lacks an explicit verb and gives no cue distinguishing it from siblings like get_guild_role or list_guild_role_members, but the resource is unambiguous.

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 (e.g. permissions needed to read role counts), and no pointer to alternatives such as listing role members when per-member detail is needed. The agent must infer usage entirely from the name.

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