Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete role

delete_role
Destructive

Deletes a Discord role after a preview and confirmation token, so members lose only that role and nothing else changes.

Instructions

Delete a role. Members holding it simply lose it; nothing else changes. Safe to call directly: the first call deletes nothing and returns a preview plus a confirm_token, and the deletion only happens when the call is repeated with that token. Prefer this gated flow over telling the user to delete the role manually.

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

NameRequiredDescriptionDefault
roleYesRole name or ID.
guildNoGuild (server) name or ID. Omit to use the default guild.
reasonNo
dry_runNo
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / description
      Added value: +"The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree."
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true and readOnlyHint=false; the description goes well beyond them by disclosing the two-phase gated protocol (first call previews and returns a confirm_token, deletion only on repeat with that token) and the blast radius (members lose the role, nothing else changes). This is exactly the mutation context an agent needs before calling a destructive tool, and it does not contradict 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and its side effects, then the safety mechanism, then the preference over manual deletion. No sentence is redundant and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema and five parameters, the description covers the action, its side effects, and the confirmation protocol, which is the core of what an agent must know. It omits permission requirements (e.g., whether the caller needs Manage Roles) and what the preview object contains beyond the token, which are modest remaining gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, with guild, reason, and dry_run effectively undocumented in the schema. The description compensates for the most important gap by explaining the confirm_token round-trip and the preview-then-confirm contract that governs both confirm_token and dry_run, leaving only reason and guild to the sparse schema text.

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" gives a specific verb and resource, and the follow-on clause "Members holding it simply lose it; nothing else changes" clarifies that the role entity itself is deleted rather than detached from a member, which is the distinction an agent needs against siblings like remove_role. It stops short of naming that sibling, so the differentiation is inferred from behavior rather than stated.

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

Usage Guidelines4/5

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

The description gives a clear usage directive: "Prefer this gated flow over telling the user to delete the role manually," which tells the agent not to punt the action back to the user. It offers no explicit when-not condition or comparison against role-management siblings such as remove_role or bulk_update_roles, so guidance is clear but not exhaustive.

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