ai-agent-channel

create_channel

Create an isolated mailbox for up to 12 named roles, returning each role's bearer token once for immediate agent delivery.

Instructions

ADMIN ONLY (HTTP transport): create a channel — an isolated mailbox shared by 2..12 named roles. Returns one bearer token per role; this is the ONLY time the tokens are shown (the server stores hashes), so deliver them to the agents now. Messages inside go to one role, a list of roles, or '*'; protected pins (team-charter, ...) need the consent of the voters each proposal declares. Names and roles are lowercase slugs (letters/digits/dash/underscore, max 64 chars).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`roles`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: ADMIN-only access, HTTP transport, one-time token display (server stores hashes), message routing rules, consent requirements for protected pins, and naming constraints. This is exceptionally transparent for a mutating tool.

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?

The description is a single, well-structured paragraph that front-loads the critical 'ADMIN ONLY' flag and then delivers dense, useful information without redundancy. Every sentence adds value—token lifecycle, message routing, consent, and naming rules—with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (which presumably describes the returned tokens), the description covers all necessary operational aspects: prerequisites, token handling, routing, consent, and naming. It is complete for an agent to call it correctly and understand the consequences.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain parameters. It does so thoroughly: names and roles must be lowercase slugs with specific character constraints and max 64 chars, and roles must be between 2 and 12. This adds significant meaning beyond the bare schema.

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 clearly states the tool's purpose: creating a channel (an isolated mailbox for 2..12 named roles). It distinguishes itself from siblings like list_channels, delete_channel, and add_role by focusing on creation. The verb 'create' plus the resource 'channel' is specific and unambiguous.

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?

It clearly states 'ADMIN ONLY' as a prerequisite and implies this is the creation tool, not for listing or deleting. It also provides critical usage context: tokens are shown only once, and protected pins require voter consent. However, it does not explicitly name alternative tools or state conditions like 'use this when you need to establish a new mailbox.'

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