Skip to main content
Glama

Coline

Mute channel

mute_channel
Idempotent

Mutes or unmutes a channel for the person: no notifications unless they're mentioned.

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>",
      "muted": "<muted>"
    },
    "name": "mute_channel"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
okYes
mutedYes

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?

The annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and repeat-call behavior are covered. The description adds genuine meaning beyond them by explaining the effect ('no notifications unless they're mentioned'), but says nothing about permissions, error cases, or reversibility beyond what the boolean implies.

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?

It is a single front-loaded sentence with the verb and resource first and the resulting behavior after the colon; nothing is redundant. It is arguably too short for the gaps it leaves, but the wording itself is efficient.

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?

The tool is simple, has an output schema, and has annotations covering safety, so most burdens are handled elsewhere. The residual gap is the `muted` parameter's direction and the absence of any permission or alternative-tool context, which the description does not fill.

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%, with the channel and workspace parameters documented in the schema but the `muted` boolean left undescribed. The description implies that 'mutes or unmutes' is driven by that flag, adding partial meaning, but it never states which value produces which state or whether the call is a set or a toggle.

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 pair and resource ('Mutes or unmutes a channel') and clarifies the effect on the target person. It does not explicitly contrast with nearby siblings such as archive_channel, leave_channel, or update_channel, which could plausibly be confused with muting.

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?

There is no when-to-use or when-not guidance, and no mention of prerequisites or which sibling to pick for a different form of channel silencing. The phrase 'for the person' does implicitly signal a personal, per-user setting rather than a workspace-wide change, but that is the only usage cue provided.

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