Skip to main content
Glama
Sign In
Capes

Capes

by Dipeshpal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

discord_set_channel_permission

Set or replace a Discord role or member's channel permission overwrite by defining allow and deny lists; unlisted permissions inherit access. Requires Manage Roles.

Instructions

Set (replace) the permission overwrite for a role or member on a channel. Permissions in neither allow nor deny inherit. Needs Manage Roles.

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": {
      "channel_id": "<channel_id>",
      "target_id": "<target_id>",
      "target_type": "<target_type>"
    },
    "name": "discord_set_channel_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
denyNoPermission names
allowNoPermission names
target_idYesRole ID or user ID (the @everyone role ID equals the server ID)
channel_idYesChannel ID (a thread ID also works)
target_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive write. The description adds real value beyond them: it discloses replacement semantics (the whole overwrite is set, not merged), the inheritance rule for permissions absent from both allow and deny, and the Manage Roles authorization requirement.

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?

Three short sentences, zero filler, and the core replace semantics are front-loaded before the inheritance note and the permission prerequisite.

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

Completeness4/5

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

For a mutation tool with annotations but no output schema, the description covers replacement semantics, inheritance, and required permissions. It omits error conditions (e.g. overwriting a higher-positioned role) and confirmation of the return value, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the schema documents most parameters. The description still adds meaning the schema lacks: that target_id is a role or member interchangeable with target_type, and the allow/deny inheritance semantics that govern how the two arrays interact.

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?

States a specific verb and resource ('Set (replace) the permission overwrite'), names both target kinds (role or member) and the scope (on a channel). This clearly separates it from discord_delete_channel_permission and discord_edit_role without needing the schemas.

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?

The word 'replace' implies this is the write-side counterpart to discord_delete_channel_permission, and 'Needs Manage Roles' gives a precondition. However, it never explicitly says when to use this versus deleting an overwrite or editing a role, so usage is only implied.

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