Skip to main content
Glama

Slack: filter channels

slack_filter_channels
Read-only

Filters Slack channels and users by typing a query into the sidebar, narrowing the visible list. Pass an empty string to clear the filter.

Instructions

Type into the sidebar's channel and user filter, narrowing the visible list. Pass an empty string to clear the filter. The Home tab must be showing (call slack_show_home first).

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": {
      "query": "<query>"
    },
    "name": "slack_filter_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesChannel or user name fragment, or empty to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the valuable non-obvious context that this only affects a UI filter and requires the Home tab to be active, though it doesn't say whether the filter persists or what happens on invalid input.

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?

Three short, front-loaded sentences: effect first, then clearing behavior, then the prerequisite. Nothing is wasted and nothing essential is buried.

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 single-parameter, UI-scoped tool with no output schema, the description covers effect, edge case, and precondition. Only minor gaps remain, such as what the visible list looks like after filtering or whether failures are surfaced.

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 100% and the schema's own description already says 'Channel or user name fragment, or empty to clear.' The description's mention of empty-string clearing therefore restates the schema rather than adding new meaning beyond it.

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

Purpose5/5

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

States a concrete verb (type into the filter) and resource (the sidebar's channel and user filter) plus the effect (narrowing the visible list). This is clearly distinguishable from siblings like slack_show_home and the code_/textedit_ tools.

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

Usage Guidelines4/5

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

Explicitly states the precondition (the Home tab must be showing, call slack_show_home first) and the clearing convention. It doesn't cover when not to use it or what happens if the precondition fails, but the essential usage path is unambiguous.

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