Skip to main content
Glama

Coline

Archive channel

archive_channel
Idempotent

Archives a channel (read-only, history kept) or brings it back. Needs a channel owner or admin.

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>",
      "archived": "<archived>"
    },
    "name": "archive_channel"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
okYes
archivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the description's job is lighter, but it still adds genuine value: it discloses that history is retained and the channel becomes read-only, and it states the required role. Minor ambiguity: 'read-only' describes the resulting channel state, not the tool, which could momentarily read against readOnlyHint=false.

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 short sentences with no filler; the core action and its reversibility come first, and the permission constraint follows. Nothing is redundant.

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?

With an output schema present, return values need not be described, and all three required parameters are fully documented in the schema. What remains is that permission failure behavior and the exact post-archive state (read-only, history retained) are only briefly touched, but the essentials for correct invocation are covered.

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%, so the schema already explains channel ids, the workspace slug, and that archived=false restores the channel. The description adds no syntax or format detail beyond that, 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?

The description gives a specific verb and resource ('Archives a channel') and covers both directions of the operation ('or brings it back'), with the key distinguishing property 'history kept' that separates it from a hard delete. It stops short of naming siblings such as delete_channel or update_channel, so the agent must infer the boundary itself.

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?

There is a real prerequisite stated ('Needs a channel owner or admin'), which is useful for gating a call, and 'brings it back' implies the un-archive path. However, there is no explicit when-to-use/when-not guidance or named alternative for permanent removal, so the routing decision against delete_channel is only implied.

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