Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_role_linked_requirements

Configure linked connection requirements for a Discord guild role, specifying the criteria members must meet to qualify for the role.

Instructions

Modify Guild Role Connection Configuration. [PUT /guilds/{guild_id}/roles/{role_id}/connections/configuration]

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

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
role_idYesRole ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already indicate this is a non-read-only, non-destructive, open-world operation. The description adds almost no behavioral context beyond the endpoint: it does not say whether existing requirements are replaced, what permissions are required, what side effects occur, or what the caller should expect after the PUT. For a mutation tool, this is a substantial transparency gap.

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?

The definition is short and front-loads the operation name followed by the endpoint in brackets. There is little wasted text, though the endpoint syntax is mostly technical metadata rather than explanatory value. The structure is efficient but minimal.

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 no output schema and an input schema that only exposes IDs and a reason field, the description should explain what configuration is being set and how the requirements are supplied. It does not address this gap, nor does it describe prerequisites or the result of the operation. The definition is too thin given the tool's complexity.

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 coverage is 100%, so guild_id, role_id, and reason are already documented in the input schema. The description adds no parameter meaning beyond that. The baseline score of 3 is appropriate because the schema does the heavy lifting and the description does not compensate with additional usage or format details.

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

Purpose3/5

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

The description states a specific resource and verb: it modifies a guild role's connection configuration via a PUT endpoint. However, it never explains what 'linked requirements' actually are, how the configuration is supplied, or how this differs from sibling tools such as get_role_linked_requirements or set_my_app_role_connection. The agent can identify the general domain but not the precise operation.

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 guidance, no prerequisites, and no comparison to alternatives. The only routing information is the raw HTTP endpoint, which does not explain when an agent should choose this tool instead of the related get or set tools. The description leaves the agent to infer usage entirely.

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