Skip to main content
Glama

Coline

Remove from channel

remove_channel_member
DestructiveIdempotent

Takes someone out of a channel. Needs a channel owner or admin; the owner can't be removed.

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>",
      "userId": "<userId>"
    },
    "name": "remove_channel_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes
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.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and non-readonly, so the safety profile is covered. The description adds real value beyond them by disclosing the authorization requirement and the hard constraint that the channel owner cannot be removed — a failure mode an agent would otherwise only discover at call time.

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 ahead of the constraint. The informal phrasing "takes someone out" costs a little precision compared with a direct "removes a member from a channel," but nothing is wasted.

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?

For a three-parameter mutation tool, the definition covers the action, the privilege required, and the one case that will always fail, while annotations handle destructiveness and idempotency and an output schema covers the response. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 67%: channel and workspace carry inline documentation, and userId is undocumented but self-evident as the member being removed, which the phrase "takes someone out" loosely confirms. The description does not add format or sourcing detail (e.g. where the userId comes from) beyond what the schema already states, so the baseline 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 someone out of a channel" gives a specific verb (remove) and resource (channel membership), which distinguishes it from channel-level tools like archive_channel or delete_channel. It does not, however, differentiate it from close siblings such as remove_member, remove_team_member, or remove_team_channel, so the agent must infer the distinction from the name alone.

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 description supplies a precondition (a channel owner or admin is required) but never states when to pick this tool over the many sibling removal tools, nor does it describe what to do instead when the target is the owner. Usage is implied by the name and the precondition rather than explicitly routed.

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