Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_edit_permission_overwrite

Allow or deny permissions for a role or member on a single Discord channel, enabling precise per-channel access control without changing server-wide role settings.

Instructions

Allow or deny permissions for a role or member on one channel.

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": {
      "guildId": "<guildId>",
      "channelId": "<channelId>",
      "targetType": "<targetType>",
      "targetId": "<targetId>"
    },
    "name": "discord_edit_permission_overwrite"
  }
}

Input Schema

NameRequiredDescriptionDefault
denyNoPermission names to deny
allowNoPermission names to allow, for example ViewChannel
reasonNo
guildIdYesDiscord id (snowflake)
targetIdYes
channelIdYes
targetTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never says whether the supplied allow/deny arrays replace or merge with existing overwrites (Discord overwrites are replace-semantics), whether the target must already have an overwrite entry, what permissions are needed, or that 'reason' lands in the audit log. For a high-stakes permission mutation these omissions matter.

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?

One tight sentence with the action and scope front-loaded and no filler. Its brevity is the only real complaint, and that is captured under the other dimensions rather than as wordiness.

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 7-parameter permission-mutating tool with no annotations and no output schema, the description covers the core action but leaves out the semantics an agent most needs: replace vs merge for allow/deny, required permissions, and effect on unlisted permissions. Adequate to identify the tool, not to call it safely.

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

Parameters2/5

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

Schema description coverage is only 43%, and the description only loosely echoes allow/deny and targetType ('role or member'). It adds nothing about the format of permission names beyond the schema's single ViewChannel example, nothing about reason, guildId, targetId, or the replace-vs-merge behavior of the arrays.

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 states a concrete action (allow or deny permissions) with a precise scope (a role or member on one channel), which distinguishes it from channel-level or role-level edit tools in the sibling list. It stops short of naming any sibling, but the verb+resource+scope is unambiguous.

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 discord_edit_channel, discord_edit_role, or discord_list_permission_overwrites/delete_permission_overwrite. Nothing notes prerequisites such as needing Manage Permissions on the channel, nor when an overwrite must be deleted rather than edited.

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