Skip to main content
Glama

Coline

Leave channel

leave_channel
Idempotent

Takes the person out of a channel. Its owner can't leave.

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": {
      "workspace": "<workspace>",
      "channel": "<channel>"
    },
    "name": "leave_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesChannel id (from list_conversations or list_channels) or its slug.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation and repeat-safety profile is covered. The description adds one genuinely new behavioral fact — the owner-cannot-leave restriction — but says nothing about membership requirements, effect on the caller's messages, or what error surfaces on the owner case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the core action is front-loaded. The second sentence is terse to the point of slight ambiguity about whose owner is meant, but it is not wasted text.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the tool is simple with only two required parameters. However, the description leaves open who exactly is removed and how the owner restriction manifests, which matters for correct invocation.

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 (workspace slug, channel id/slug) are documented in the schema itself. The description adds no additional meaning about parameter formats or interactions, so the baseline of 3 applies.

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?

"Takes the person out of a channel" states a concrete verb and resource, and the follow-up clause implies the actor is the member themself rather than an arbitrary user. It does not explicitly distinguish itself from remove_channel_member or leave_direct_message, so an agent must infer the self-leave semantics from the owner clause.

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

Usage Guidelines2/5

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

The only usage rule given is the precondition that a channel owner cannot leave. There is no statement of when to prefer this over remove_channel_member (removing someone else) or leave_direct_message, and no mention of what to do when the call fails for an owner.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources