discord_list_channelsLists channels in a Discord guild by guild ID, helping you inspect server structure and identify available channels for management or backup planning.
List channels in a Discord guild.
| Name | Required | Description | Default |
|---|---|---|---|
| guildId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| error | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds no behavioral context beyond restating that it lists channels—no mention of rate limits, pagination, or authentication requirements—so it contributes little beyond the structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with zero wasted words. It gets straight to the point and is appropriately sized for a simple list operation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and comprehensive annotations, the description covers the basic purpose adequately. However, it omits parameter semantics (guild ID format) and behavioral details like pagination, leaving some gaps for an agent to infer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate by explaining the sole parameter guildId. It only says 'in a Discord guild,' which vaguely implies a guild identifier but gives no details on format, source, or required pattern, adding minimal meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('List') and resource ('channels') within a clear scope ('in a Discord guild'). This distinguishes it from siblings like discord_get_channel (single channel) and discord_list_guilds (guilds), so an agent can immediately understand its purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives such as discord_get_channel for detailed channel info. It also omits prerequisites (e.g., required permissions) and any conditions or exclusions, leaving usage entirely implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
This server cannot be deployed