Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_prune

Read-onlyDestructive

Count members a Discord guild prune would remove after N inactive days, optionally filtered by roles.

Instructions

Count members a prune would remove (inactive for N days). [GET /guilds/{guild_id}/prune]

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

Input Schema

NameRequiredDescriptionDefault
daysNodays
guild_idYesServer (guild) ID
include_rolesNoinclude roles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the read-only nature is covered; the description adds the useful semantic that this is a count/preview keyed on inactivity days. It does not resolve the tension with destructiveHint=true, nor does it state that no members are modified, what the response shape is, or any permission requirements. Useful but not rich beyond the annotations.

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 compact sentence with the core behavior front-loaded, followed by the HTTP route as a convention tag. Nothing is padded, though the bracketed endpoint adds little for an MCP caller.

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?

There is no output schema, so the description should indicate what comes back (a count) and whether it is a dry-run guarantee; "count" hints at an integer result but the return shape and the effect of include_roles remain unstated for a three-parameter tool.

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%, but the schema text is near-useless ("days": "days", "include_roles": "include roles"). The description clarifies `days` as the inactivity window for the prune calculation, which is real added meaning, but says nothing about how `include_roles` affects which members are counted.

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?

"Count members a prune would remove (inactive for N days)" gives a specific verb (count), a specific resource (prune-eligible members), and the qualifying criterion. It is clearly distinguishable from a mutating prune, though it never names prune_guild as the counterpart that actually removes them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the fact that it counts rather than removes suggests a dry-run/preview check before an actual prune, but the description never states when to call this versus prune_guild or whether it is a prerequisite step.

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