Skip to main content
Glama

List channels

discord_list_channels
Read-only

Lists the Discord channels this server can read, grouped by category, with channel type, posting permission, and available forum tags.

Instructions

List the channels this server can read, grouped by category, with type, whether it can post there, and for forums the available tags.

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": "discord_list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 openWorldHint=true. The description adds useful behavior beyond that: it only returns channels the server can read, groups results by category, reports postability, and includes forum tags. It does not mention pagination or error behavior, but the added return-context is substantive.

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?

A single front-loaded sentence with no wasted wording. It efficiently packs scope, grouping, and return attributes into one readable statement.

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?

Because no output schema exists, the description needs to explain return values, and it does: grouped categories, channel type, postability, and forum tags. It is nearly complete for a zero-parameter listing tool, though the pronoun 'it' in 'whether it can post there' is mildly ambiguous and pagination behavior is unstated.

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 are no parameter semantics for the description to clarify. The empty schema is consistent with the description, and the baseline for a zero-parameter tool applies.

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 (List) and resource (channels), scopes it to channels the server can read, and specifies the returned shape: group, type, postability, and forum tags. It is clearly distinguishable from channel-admin siblings.

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?

Usage is implied as channel discovery, but there is no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as discord_list_forum_tags or discord_admin_get_channel. An agent can infer the use case but must decide on its own when this tool is preferable.

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