Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_modify_role

Modify a Discord role's name, color, hoist, or mentionable status using its role ID. Target a specific server with guild_id or default to the active server.

Instructions

Modify an existing role's name, color, hoist, or mentionable status.

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_id": "<role_id>"
    },
    "name": "discord_modify_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew role name.
colorNoRGB integer color.
hoistNoDisplay role separately.
role_idYesThe ID of the role to modify.
guild_idNoServer ID (defaults to active server).
mentionableNoAllow @mention.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It says 'modify' but never states that this is a mutating, non-reversible operation, what permissions are required, whether omitted fields are left untouched, or what happens on failure — all material for a write tool.

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 compact sentence with the verb and affected fields front-loaded and no filler. It is concise to a fault — the brevity is the source of the missing behavioral guidance rather than padding.

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 mutation tool with zero annotations and no output schema, the description should cover permission requirements, side effects, and field-omission behavior; it covers none of these. The complete parameter schema is the only thing keeping this callable.

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%, so every parameter is already documented in the schema. The description merely echoes the same field list (name, color, hoist, mentionable) without adding semantics such as color format details or default-server behavior for guild_id. Baseline 3 applies.

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?

States a specific verb+resource ('Modify an existing role') and enumerates the four mutable fields, which clearly separates it from create_role/delete_role by name alone. It stops short of explicitly contrasting with the other role siblings (assign_role, remove_role), so it is not a 5.

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?

No indication of when to use this versus discord_create_role, discord_assign_role, or discord_modify_guild, and no prerequisites stated (e.g. Manage Roles permission, role hierarchy constraints). The agent must infer everything from the name.

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