Skip to main content
Glama
Sign In
@striderlabs/mcp-discord

@striderlabs/mcp-discord

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_channels

List all Discord server channels by providing the server ID, with optional filtering by text, voice, category, or all types.

Instructions

List all channels in a Discord server

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": {
      "server_id": "<server_id>"
    },
    "name": "get_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
server_idYesThe Discord server (guild) ID
channel_typeNoFilter by channel type (default: text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It does not mention the channel_type default of 'text', which conflicts with the claim of listing 'all channels'. This is a meaningful gap because a caller relying on the description may expect voice/category channels by default.

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?

The description is a single, efficient sentence that immediately conveys the tool's purpose. There is no wasted wording, and the main action and target resource are front-loaded.

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, but the description omits the fact that channel_type defaults to 'text', making 'all channels' potentially misleading. Without an output schema, a bit more detail about the default filtering behavior would make the description fully self-sufficient.

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 documents both parameters and the enum values. The description adds no additional semantic detail beyond what the schema provides, so the baseline of 3 is appropriate.

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?

The description names a specific verb ('List'), resource ('all channels'), and scope ('in a Discord server'). It clearly distinguishes get_channels from sibling tools like get_messages, send_message, get_dms, and get_servers, which target different resources.

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?

The intended use case is clear: retrieve channels for a server. It does not explicitly say when not to use this tool, but the resource-based separation from sibling tools makes the appropriate context unambiguous.

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

Deploy Server

Other Tools