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

Clone role

clone_role

Copy a Discord role's permissions, color, and settings into a new role to duplicate access levels without manual reconfiguration.

Instructions

Copy a role's permissions, color, and settings into a new role.

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": "clone_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRole name or ID to copy.
guildNoGuild (server) name or ID. Omit to use the default guild.
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive write, and the description usefully adds what is carried over (permissions, color, settings). It does not disclose whether members holding the source role are assigned the clone, what permissions the caller needs, or how the new role is named if new_name is omitted.

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?

A single tight sentence with the action and the copied attributes front-loaded and no filler. It is efficient, though its brevity is part of why it under-serves the mutation semantics.

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?

This is a mutation tool with no output schema, so the description should say what comes back (e.g. the new role identifier) and how the clone is named. With three parameters, one of them undocumented in the schema, the definition leaves real gaps an agent needs filled before calling.

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

Parameters2/5

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

Schema coverage is only 67% and the undocumented new_name parameter is a length-constrained string whose default behavior (fallback naming) is exactly what the description should clarify. The description adds no per-parameter meaning beyond restating that a role is copied, leaving the guild scoping and naming semantics entirely to the schema.

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 sentence pairs a specific verb ("Copy") with a specific resource (a role's permissions, color, and settings) and states the outcome is a new role, which separates it from a bare create or update. It stops short of naming the siblings it differs from, notably create_role and update_role.

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 or when-not-to-use guidance, and no mention of the obvious alternative create_role for building a role from scratch. The agent must infer that this tool is for duplicating an existing role rather than defining one.

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