Skip to main content
Glama

sockdock_list_channels

Read-only

Lists Slack channels the app has been added to so you can pick or verify a valid channel before saving a rule. If a channel is missing, invite the app there first.

Instructions

Lists the Slack channels the Slack app has been added to; a rule can only use one of these. Use it before sockdock_save_rule to pick or check a channel. If the list is empty or lacks the channel the user wants, the Slack app has not been added there: ask the user to type /invite in that channel. A problem of missing_scope means the Slack app lacks channels:read/groups:read; then pass a channel ID instead. The first entry, dm, stands for DMs to the Slack app; its problem missing_scope means the Slack app lacks im:history (ask the user to add it with the message.im event and the Messages tab, and reinstall).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sockdock_list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
problemNowhy the list is incomplete, e.g. missing_scope (add channels:read and groups:read to the Slack app)
channelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so this description is not obligated to cover safety, but it adds substantial behavior beyond that: the meaning of the special first entry 'dm', and the interpretation and remediation of missing_scope for both channels and DMs. That error semantics is exactly the kind of context annotations cannot express.

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?

Sentences are front-loaded with purpose and usage, then degrade into error branches that each carry distinct remediation steps, so nothing is padding. The final sentence about 'dm' and im:history is dense and stacked with parenthetical instructions, which slows scanning slightly.

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?

With an output schema present, the description needn't explain return values, and it correctly focuses on the non-obvious parts: which channels appear, the special 'dm' entry, and how to recover from missing_scope. Nothing an agent needs to call this correctly or interpret a bad result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline is 4. The description spends its space on result interpretation, which is more useful here than parameter detail.

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 specific verb and resource ('Lists the Slack channels the Slack app has been added to') and immediately narrows scope with the constraint that 'a rule can only use one of these'. That scoping distinguishes it from any broader channel-listing expectation and from sibling rule tools.

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

Usage Guidelines5/5

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

Explicitly says to call it before sockdock_save_rule 'to pick or check a channel', naming the sibling it precedes and the reason. It also gives branch guidance for a channel that is absent (ask the user to type /invite) and for a missing_scope result (pass a channel ID instead).

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