discp

upsert_member_channel_permissions

Create or update a channel permission overwrite for an individual member, specifying allowed and denied permissions.

Instructions

Create or update channel permission overwrite for an individual member

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

Input Schema

Name	Required	Description
`reason`	No	Audit log reason
`userId`	Yes	Member User ID
`denyRaw`	No	Denied permissions raw bitfield string
`allowRaw`	No	Allowed permissions raw bitfield string
`channelId`	Yes	Channel ID
`denyPermissions`	No	CSV of denied permission names
`allowPermissions`	No	CSV of allowed permission names

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 2, 2026

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 burden. 'Create or update' implies mutation and idempotency, but it does not disclose permission requirements, whether it overwrites existing overwrites, the effect of omitted fields (e.g., clearing permissions), or the audit logging behavior (though the 'reason' parameter hints at it).

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?

The description is a single, efficient sentence that front-loads the action and resource. It wastes no words, though it could potentially include a second sentence for crucial context without harming conciseness.

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 no annotations, no output schema, and 7 parameters, the description is incomplete. It omits required permissions, idempotency semantics, overwrite behavior, and interaction with role-based overwrites. An agent would need to infer these from the name, which is risky for a permission-changing operation.

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 coverage is 100%, so all 7 parameters are documented in the schema. The description adds no parameter details beyond what the schema provides (e.g., bitfield vs CSV format, required vs optional). Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific verb ('Create or update'), resource ('channel permission overwrite'), and target ('for an individual member'). This distinguishes it from the sibling 'upsert_role_channel_permissions', though the distinction is implicit rather than explicit. It's clear but could more directly contrast with the role-based sibling.

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?

No when-to-use guidance, no prerequisites (e.g., required permissions like 'Manage Roles'), and no explicit alternatives or exclusions. The agent must infer context from the name and sibling list. For a permission-mutating tool, this is a significant gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server