Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by tensakulabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_list_channels

Lists all text channels in a Discord guild. Provide a guild ID to get channel names and identifiers.

Instructions

List text channels in a guild.

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": {
      "guildId": "<guildId>"
    },
    "name": "discord_list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildIdYesGuild ID from discord_list_guilds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden. The description only says 'list text channels', omitting details like rate limits, permission requirements, or behavior on invalid guild IDs. It doesn't disclose whether it returns only channel names or full objects.

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?

The description is a single sentence, concise and front-loaded. It contains no unnecessary words, but could be slightly expanded to include usage hints without being verbose.

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?

Given the tool's simplicity (one required parameter, list operation), the description is somewhat adequate. However, without an output schema, the agent lacks information about the return format (e.g., list of channel IDs, names, or objects), reducing completeness.

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%, with the parameter description 'Guild ID from discord_list_guilds' providing context. The tool description adds no extra meaning beyond the schema, meeting the baseline for high coverage.

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 clearly states the tool lists text channels in a guild, using a specific verb and resource. It distinguishes from siblings like discord_list_guilds (lists guilds) and discord_get_dms (gets direct messages), so the purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., discord_search, discord_get_messages). The description only states what the tool does, without mentioning prerequisites or context where this tool is appropriate.

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