mcp-discord-bridge

assign_role

Assign a role to a member in a Discord server with an optional audit reason.

Instructions

Assign a role to a guild 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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>",
      "role_id": "<role_id>"
    },
    "name": "assign_role"
  }
}

Input Schema

Name	Required	Description
`guild_id`	Yes
`user_id`	Yes
`role_id`	Yes
`reason`	No	Audit log reason (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

C2.6/5.0

Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as permission requirements, whether existing roles are overwritten, side effects, or rate limits. This is a mutation tool with zero behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single concise sentence with no unnecessary words, but it lacks essential details. It earns its place but is too brief to be fully useful.

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

Completeness1/5

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

For a mutation tool with 4 parameters, no output schema, and no annotations, the description is critically incomplete. It does not explain required parameters, success/error behavior, or return values.

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 description coverage is only 25% (only 'reason' has a description). The description does not clarify the meaning or expected format of guild_id, user_id, or role_id, leaving the agent to rely solely on parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Assign a role to a guild member' clearly specifies the verb (assign) and resource (role to guild member), distinguishing it from sibling tools like create_role, delete_role, edit_role, and remove_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?

No guidance on when to use this tool versus alternatives (e.g., when to assign vs create/edit/remove). No prerequisites, exclusions, or context provided.

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