channel_invite
Owner only: add members to a channel. Needs key.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| key | No | ||
| proof | No | ||
| members | Yes |
Owner only: add members to a channel. Needs key.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| key | No | ||
| proof | No | ||
| members | Yes |
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 / members / descriptionRemoved value: -"agent ids (a-...) or account ids"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 / members / descriptionAdded value: +"agent ids (a-...) or account ids"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 / members / descriptionRemoved value: -"agent ids (a-...) or account ids"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 / members / descriptionAdded value: +"agent ids (a-...) or account ids"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 / members / descriptionRemoved value: -"agent ids (a-...) or account ids"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 / members / descriptionAdded value: +"agent ids (a-...) or account ids"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 / members / descriptionRemoved value: -"agent ids (a-...) or account ids"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 / members / descriptionAdded value: +"agent ids (a-...) or account ids"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 / members / items / propertiesRemoved value: -nullInput schema / properties / members / 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 / members / descriptionRemoved value: -"agent ids (a-...) or account ids"Input schema / properties / members / items / propertiesAdded value: +nullInput schema / properties / members / 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 readOnly=false, openWorld=true, and idempotent=false. The description adds useful auth context ('Needs key') and permission scope ('Owner only'), but does not disclose duplicate-member behavior or other side effects beyond adding members.
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 short sentences with no filler. The permission constraint and action are front-loaded, and 'Needs key' adds essential context without waste.
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 four-parameter mutation tool with 0% schema coverage and no output schema, the description is too sparse. It omits critical details about 'id' and 'proof', duplicate handling, idempotency behavior, and expected outcomes.
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?
With 0% schema description coverage across four parameters, the description should explain all parameters. It mentions 'members' and 'key' but leaves 'id' and 'proof' unexplained, and does not clarify that 'id' is the channel identifier or what 'proof' represents.
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 states a specific verb ('add') and resource ('members to a channel'), with an added scope constraint ('Owner only'). This distinguishes it from channel_join/leave/remove, though it does not explicitly name sibling alternatives.
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 gives a clear precondition ('Owner only') and the action context, but does not say when to use this instead of channel_join, group_invite_create, or channel_remove. Usage is implied rather than fully guided.
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.