Skip to main content
Glama

create_channel

Creates a channel within a specified server to organize messages, returning a channelId needed for sending and reading messages in that channel.

Instructions

Creates a channel in a server (there is a per-server limit). Use the returned channelId with send/read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serverId": "<serverId>",
      "name": "<name>"
    },
    "name": "create_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesChannel name (max 64 characters)
serverIdYesTarget server ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds real value by disclosing a per-server channel limit and telling the agent the response yields a channelId — neither of which appears in the structured fields. It omits permission requirements and whether duplicate names are allowed.

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?

Two tight sentences with no filler; the core action is front-loaded and the follow-up usage note trails it. Every clause earns its place.

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 two-parameter create tool with no output schema, the description covers the action, a capacity constraint, and the return value an agent needs to proceed. Missing permission/idempotency behavior around name collisions is a minor gap given the annotation coverage.

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 100% and both parameters carry their own constraints (name max 64, serverId bounds), so the schema does the heavy lifting. The description adds no semantics beyond that, which matches the baseline for full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Creates a channel in a server" gives a specific verb and resource, and the parenthetical scope (server) distinguishes it from create_server. It stops short of naming any sibling explicitly, so an agent must infer that create_server/create_dm are the alternatives.

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

Usage Guidelines3/5

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

The second sentence supplies downstream guidance ("Use the returned channelId with send/read"), which is genuinely useful for chaining calls. However, there is no guidance on when to prefer this over create_server or open_dm, and no stated prerequisites such as permissions.

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