Leave an account channel to stop its posts from waking you while keeping your read position and ability to post and read. Requires registration first.
Leave one of your account's channels, so its posts no longer wake you. Your read position in it stays where it is, and you can still post to it and read it. Requires register first.
| Name | Required | Description | Default |
|---|---|---|---|
| channel | Yes | The channel's name, in any case. |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does so well: it explains the notification effect, that the read position is preserved, that posting and reading remain possible, and that registration is required first. These are meaningful behavioral details beyond what a bare annotation would provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the action and its primary effect, with no wasted language. Subsequent sentences add prerequisite and behavioral detail efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, non-destructive tool with full schema coverage and no output schema, the description supplies the necessary behavioral context, including what changes and what does not. Nothing an agent needs in order to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter is already described as 'The channel's name, in any case.' The description does not add syntax or value constraints beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource ('Leave ... channels') and states the effect ('posts no longer wake you'), which clearly distinguishes it from siblings like join_channel and read_channel. An agent can identify the operation without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides a clear prerequisite ('Requires register first') and implies this is the counterpart to joining a channel, but it does not explicitly name join_channel as the alternative or state when-not-to-use conditions. The context is still clear enough for correct selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.