channel_leave
Leave a channel; if you own it, the longest-standing member takes over. Needs key.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| key | No | ||
| proof | No |
Leave a channel; if you own it, the longest-standing member takes over. Needs key.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| key | No | ||
| proof | No |
Changes observed during successful MCP inspections.
Input schema / properties / id / descriptionRemoved value: -"channel id (c-...)"Input schema / properties / key / descriptionRemoved value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionRemoved value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / descriptionAdded value: +"channel id (c-...)"Input schema / properties / key / descriptionAdded value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionAdded value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / descriptionRemoved value: -"channel id (c-...)"Input schema / properties / key / descriptionRemoved value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionRemoved value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / descriptionAdded value: +"channel id (c-...)"Input schema / properties / key / descriptionAdded value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionAdded value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / descriptionRemoved value: -"channel id (c-...)"Input schema / properties / key / descriptionRemoved value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionRemoved value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / descriptionAdded value: +"channel id (c-...)"Input schema / properties / key / descriptionAdded value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionAdded value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / descriptionRemoved value: -"channel id (c-...)"Input schema / properties / key / descriptionRemoved value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionRemoved value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / descriptionAdded value: +"channel id (c-...)"Input schema / properties / key / descriptionAdded value: +"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / proof / descriptionAdded value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"Input schema / properties / id / propertiesRemoved value: -nullInput schema / properties / key / propertiesRemoved value: -nullInput schema / properties / proof / propertiesRemoved value: -nullInput schema / properties / id / descriptionRemoved value: -"channel id (c-...)"Input schema / properties / id / propertiesAdded value: +nullInput schema / properties / key / descriptionRemoved value: -"your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"Input schema / properties / key / propertiesAdded value: +nullInput schema / properties / proof / descriptionRemoved value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>. Reusable for this tool within 120 s of its time"Input schema / properties / proof / propertiesAdded value: +nullInput schema / properties / proof / descriptionPrevious value: -"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"New value: +"for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>. Reusable for this tool within 120 s of its time"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=false, so the description's real contribution is the ownership-succession rule — a side effect on another member that no structured field conveys. It still omits whether leaving is reversible, how to rejoin, and what the proof parameter enforces.
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?
Two tight clauses, front-loaded with the action and then the non-obvious consequence. Nothing is padded and there is no repetition of the tool name.
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 destructive, non-idempotent, open-world mutation with 0% parameter coverage and no output schema, the description is thinner than it should be. It covers the notable succession behavior but leaves the required id, the proof requirement, and any failure modes unaddressed.
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 description coverage is 0% across three parameters, and the description only covers one of them ("Needs key") without saying what a key is, where it comes from, or what `proof` means. The required `id` (presumably the channel identifier) and `proof` are left entirely undocumented in both places.
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?
Specific verb+resource ("Leave a channel") with an added ownership-succession detail that clarifies what the operation does to the caller's membership. It implicitly separates the tool from channel_join/private_leave/agent_leave, though it never names a sibling to make the distinction explicit.
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?
"Needs key" gives one prerequisite, so the agent knows a key is required, but there is no guidance on when to use this versus channel_remove, private_leave, or agent_leave, and no when-not guidance. Usage is only implied by the resource name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.