Skip to main content
Glama

Unlock channel

unlock_channel

Remove the send-message denial from the everyone overwrite to unlock a Discord channel, allowing all members to send messages.

Instructions

Reverse lock_channel by removing the send-message denial from the everyone overwrite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesChannel name or ID.
guildNoGuild (server) name or ID. Omit to use the default guild.
reasonNo
Behavior4/5

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds context that it targets the everyone overwrite and reverses a specific denial, which is useful beyond annotations.

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?

Single sentence, front-loaded with the action, no wasted words.

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 simple mutation tool with no output schema and clear annotations, the description is sufficient. Could mention edge cases like if the overwrite doesn't exist, but overall complete.

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 67% (channel and guild have descriptions, reason only has maxLength). The description does not add meaning beyond the schema, so baseline 3 applies.

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?

The description uses a specific verb ('reverse') and resource ('lock_channel by removing the send-message denial from the everyone overwrite'), clearly distinguishing it from the sibling tool 'lock_channel'.

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

Usage Guidelines4/5

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

The description implicitly states when to use (after locking) but does not explicitly mention when not to use or alternatives like 'set_channel_permissions' for fine-grained control.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OrygnsCode/Omnicord'

If you have feedback or need assistance with the MCP directory API, please join our Discord server