Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_assign_role

Assigns a Discord role to a server member using user and role IDs, with an optional guild ID or the active server for role management.

Instructions

Assign a role to a server member.

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": {
      "user_id": "<user_id>",
      "role_id": "<role_id>"
    },
    "name": "discord_assign_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesThe ID of the role to assign.
user_idYesThe ID of the user.
guild_idNoServer ID (defaults to active server).

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?

With no annotations, the description carries the full burden for a mutation tool, yet it says nothing about required permissions, whether assigning an already-assigned role is idempotent, what happens on invalid user/role IDs, or whether the change is logged/reversible. Only the bare mutation intent is conveyed.

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 front-loaded sentence with zero padding or redundant restatement of the title. It is as tight as possible, though the brevity edges into under-specification rather than efficient completeness.

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 permission-gated Discord mutation with no annotations and no output schema, the description omits everything an agent needs beyond the happy path: permission prerequisites, failure modes, and confirmation of effect. The fully-covered schema is the only thing preventing a 1.

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 user_id, role_id, and the guild_id default are already fully documented in the structured data. The description adds no syntax, format, or ID-resolution guidance beyond what the schema provides, making the baseline 3 appropriate.

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 ('Assign') and resource ('role') applied to a server member, which cleanly separates it from the sibling discord_remove_role and discord_modify_role. It stops short of explicitly naming those siblings or stating scope conditions, but an agent can identify the operation without opening the schema.

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 guidance on when to use this versus discord_remove_role, discord_modify_member, or discord_modify_role, nor any prerequisites such as requiring Manage Roles permission or the bot's role being higher in the hierarchy. The agent must infer all usage conditions.

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