Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_prune_members

Preview or run an inactivity-based Discord member prune; role-assigned members are excluded automatically.

Instructions

Preview or run a member prune by inactivity. Members with roles are never pruned by Discord.

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": {
      "guildId": "<guildId>"
    },
    "name": "discord_prune_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
dryRunNo
reasonNo
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does supply one genuinely important safety fact: members with roles are never pruned by Discord. It also signals a preview mode. However, it omits that the operation is destructive/irreversible, what permissions are needed, and whether a count of pruned members is returned.

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?

Two short sentences, zero filler, with the action/scope front-loaded and the safety caveat immediately after. Nothing could be removed without losing meaning.

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 four-parameter, destructive, annotation-free tool with no output schema, the definition covers the core action and one critical exclusion but leaves permission requirements, irreversibility, and result shape unstated. Adequate, not complete.

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 only 25% (guildId alone is described), so the description must compensate. It indirectly explains dryRun via "Preview or run" and days via "inactivity", but the reason parameter gets no mention and no defaults or bounds are restated.

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 gives a specific verb and resource ("prune" + "members") plus the criterion ("by inactivity"), which cleanly separates it from siblings like discord_list_members or discord_ban_member. It stops short of naming an explicit alternative caller path, but the action 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 Guidelines3/5

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

"Preview or run" implies the two modes of operation and the inactivity criterion implies the use case, but there is no explicit when-to-use versus when-not guidance and no named alternatives (e.g. individual kick or list-then-filter). Usage is inferable rather than stated.

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