Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_role

Read-only

Retrieves details for a specific role in a Discord server using the guild ID and role ID, supporting role lookup and permission checks.

Instructions

Get Guild Role. [GET /guilds/{guild_id}/roles/{role_id}]

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_guild_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesRole ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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. The description adds only the raw REST endpoint path, which conveys no behavioral context such as permission requirements, failure modes for invalid role IDs, or what the response contains.

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 fragments with zero padding and the purpose front-loaded. It is efficient, though the bracketed endpoint is arguably filler for an agent that never sees the transport layer.

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

Completeness3/5

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

For a simple two-parameter read with full annotation coverage and no output schema, the definition is minimally sufficient. However, it says nothing about what a role object contains or what happens when the role does not exist, leaving gaps an agent may need to fill empirically.

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% and both parameters carry their own descriptions, so the baseline is 3. The endpoint template does show guild_id and role_id as path segments, but that adds no meaning beyond the schema.

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?

"Get Guild Role" names a specific verb and resource, so an agent knows this fetches a single role. But the description is essentially the tool name restated plus an HTTP path, with no differentiation from siblings such as get_guild_role_member_counts or the create/modify/delete role tools beyond the name itself.

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 list_guild_role_members or get_guild, and no stated prerequisites or exclusions. The only implicit signal is that both guild_id and role_id are required, which an agent must infer from the schema.

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