discord-server-mcp

delete_role

Destructive

Permanently removes a Discord role from a server and requires confirmation to prevent accidental deletion.

Instructions

Delete a role. Cannot be undone.

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": {
      "role": "<role>"
    },
    "name": "delete_role"
  }
}

Input Schema

Name	Required	Description
`bot`	No	Use this bot (name or id) instead of choosing automatically
`role`	Yes
`reason`	No	Reason shown in the server's audit log
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`confirm`	No	Must be true to really do this permanent action; without it you get a preview
`dry_run`	No	Show the requests that would be made without changing anything

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so "Cannot be undone" largely restates structured data. The description omits genuinely additive behavior: that the action is preview-only unless confirm=true, that dry_run exists, that a reason is logged to the audit trail, and what happens to members holding the role.

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?

Two short sentences with no filler, and the destructive warning is front-loaded after the action statement. It is efficient, though the brevity borders on under-specification rather than economy.

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?

For a permanent, six-parameter mutation with no output schema, the description leaves out the confirm/preview safety mechanism and the audit-log reason behavior, both of which change how an agent should call it. Annotations cover the destructive classification but not the workflow.

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 83%, so the parameters (bot, reason, server, confirm, dry_run) are already documented in the schema. The description adds no meaning about any of them, which is the expected baseline when the schema does the heavy lifting.

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?

"Delete a role" names a specific verb and resource, which is enough to distinguish it from create_role and edit_role among the siblings. It stops short of any explicit sibling differentiation, but the purpose 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 beyond the implicit meaning of "delete". Nothing tells the agent when to prefer edit_role (e.g. removing permissions rather than the role) or what prerequisites exist, and the only caution offered is "Cannot be undone."

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