Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_get_channel_permissions

Read-only

List every permission overwrite on a Discord channel, with allowed and denied flags per role and member. Use it to inspect channel-specific access before making permission changes.

Instructions

List every permission overwrite on a channel, per role and per member, with the allowed and denied permission flags for each. Read-only. Use discord_audit_permissions for a server-wide report across all channels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesID (snowflake) of the channel to inspect.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
overwritesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "overwrites": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "allow": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "deny": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "type",
+          "allow",
+          "deny"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "overwrites"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel to inspect."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, and the description adds meaningful behavioral detail beyond that: it discloses the exact structure of results (per role and per member, allowed and denied flags) and the comprehensive 'every permission overwrite' scope. This is useful context that annotations alone do not provide.

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

Conciseness5/5

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

Two compact sentences with no filler. The core behavior is front-loaded first, the read-only property is stated briefly, and the alternative routing is in the second sentence. Every sentence earns its place.

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

Completeness5/5

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

For a single-parameter, read-only listing tool with an output schema present, this description is complete. It covers scope, result granularity, safety, and the main alternative tool. Nothing that an agent needs to select or invoke this correctly is missing.

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?

The input schema has 100% description coverage for channel_id, including its snowflake pattern and purpose. The description only refers to 'a channel' generically, so it adds little beyond the schema. A baseline of 3 is appropriate because the schema already carries the parameter documentation burden.

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?

Description states a specific verb ('List') and resource ('every permission overwrite on a channel'), and clearly explains the granularity: per role and per member, with allowed and denied flags. It differentiates itself from discord_audit_permissions by explicitly naming that sibling, so an agent can distinguish the tools.

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

Usage Guidelines5/5

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

It explicitly provides the alternative tool ('discord_audit_permissions') and the condition that should trigger its use ('server-wide report across all channels'). This gives clear routing guidance without needing to infer from tool names.

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