Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_role_linked_requirements

Read-only

Retrieves the connection configuration for a Discord guild role, detailing the linked requirements members must meet to be assigned the role.

Instructions

Get Guild Role Connection Configuration. [GET /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": "get_role_linked_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesRole ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without description help. The only extra the description adds is the raw GET path, which confirms it is a per-guild, per-role read but reveals nothing about auth scope, error cases, or what the configuration contains. Marginal value beyond annotations.

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?

Two short clauses, front-loaded with the action and followed by the endpoint reference; nothing is padded or redundant. It is arguably too terse rather than too long, but it is structurally clean.

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?

With no output schema, the description is the only place to learn what a "role connection configuration" returns, and it says nothing about shape or content. For a read tool whose return value is undefined elsewhere, this is a notable omission, though the two required params are fully covered by the schema.

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%: both required parameters (guild_id, role_id) are documented in the schema as "Server (guild) ID" and "Role ID". The description adds no syntax, format, or constraint detail beyond that, so the 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?

The description gives a specific verb+resource ("Get Guild Role Connection Configuration") and the underlying endpoint, which pairs with the name get_role_linked_requirements. It is understandable in isolation, but it never contrasts with the write-side sibling set_role_linked_requirements, and the mismatch between "linked requirements" (name) and "connection configuration" (description) leaves slight ambiguity about what is actually returned.

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 statement of when to call this tool, no preconditions (e.g., needing a role connection app configured), and no reference to the counterpart set_role_linked_requirements for modifying the same resource. Usage must be inferred entirely 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