Skip to main content
Glama
Sign In
discp

discp

by SharimAli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

upsert_role_channel_permissions

Create or update a Discord channel permission overwrite for a role, setting allowed and denied permissions by ID or CSV.

Instructions

Create or update channel permission overwrite for a role

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": {
      "channelId": "<channelId>",
      "roleId": "<roleId>"
    },
    "name": "upsert_role_channel_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason
roleIdYesRole ID
denyRawNoDenied permissions raw bitfield string
allowRawNoAllowed permissions raw bitfield string
channelIdYesChannel ID
denyPermissionsNoCSV of denied permission names
allowPermissionsNoCSV of allowed permission names (e.g. ViewChannel,SendMessages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses upsert semantics (create or update), which is useful, but says nothing about required permissions, how allow/deny interact, whether existing overwrites are replaced or merged, or audit-log behavior despite the reason parameter.

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 front-loaded sentence with no filler or redundancy. It is efficient, though extremely minimal and could afford one clause of guidance without becoming bloated.

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

Completeness2/5

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

For a mutation tool with seven parameters, no annotations, and no output schema, the description is too thin. It omits prerequisites, the effect on existing overwrites, and interaction between allow/deny inputs, leaving the agent under-informed about consequences.

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%, so the schema already documents all seven parameters, including allowRaw/denyRaw and the CSV permission lists. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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 gives a clear verb pair (create or update) and a precise resource (channel permission overwrite for a role), which distinguishes it in kind from the member-scoped sibling upsert_member_channel_permissions. It stops short of naming that sibling explicitly, so it is clear but lacks sibling differentiation.

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 statement of when to use this tool versus delete_channel_permission, list_channel_permissions, or upsert_member_channel_permissions. The upsert wording implies create-or-update behavior but no conditions, prerequisites, or alternatives are given.

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