Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_my_permissions

Read-only

Computes your effective Discord permissions in a server or specific channel from roles and overwrites, helping you verify access before acting.

Instructions

Your effective permissions in a server, or in a specific channel (computed from roles and overwrites).

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

Input Schema

NameRequiredDescriptionDefault
guild_idYes
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior context by stating permissions are computed from roles and overwrites rather than stored, hinting that results are derived and may change. It says nothing about the shape of the returned permission set, caching, or what happens if the channel does not belong to the guild.

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 compact sentence with the scope constraint front-loaded and the computational nuance parenthetically attached. No filler, though one more clause on the optional channel parameter would have been worth its space.

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 two-parameter read tool with annotations and no output schema, the definition covers purpose and derivation adequately but leaves the return value undefined (permission list? bitfield? per-channel breakdown?) and does not clarify the optionality of channel_id. An agent could invoke it, but only by guessing at the response shape.

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 0%, so the description must carry the param meaning, and it partially does by mapping 'in a server' to guild_id and 'in a specific channel' to channel_id. It does not state that guild_id is required while channel_id is optional, nor any format expectations (snowflake IDs) or the constraint that channel_id must belong to guild_id.

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?

Names a specific resource ('your effective permissions') and scope (a server, or a specific channel), which distinguishes it from the many mutation-oriented permission siblings like modify_channel_permissions. The parenthetical explaining derivation from roles and overwrites sharpens what 'effective' means. It lacks an explicit verb but is unambiguous about what is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call this to check your own permissions in a guild or a channel. There is no explicit when-to-use versus when-not, and no guidance on when to supply channel_id versus omitting it, or how this differs from listing guild application command permissions siblings.

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