Skip to main content
Glama
Yv3s-y4ng

MCP-Discord Stream

by Yv3s-y4ng

discord_get_forum_channels

Retrieve all forum channels from a Discord server by providing its guild ID. Organize and manage Discord forums efficiently.

Instructions

Lists all forum channels in a specified Discord server (guild)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYes
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the action (lists) but does not cover return format, authentication requirements, pagination, or any rate limits. For a simple read tool this is minimal but still lacking.

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 concise sentence that directly states the tool's action and scope. No unnecessary words or repetition.

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?

With only one parameter, no output schema, and no annotations, the description covers the essential purpose and input. While it does not describe the return value, the tool is simple enough that the output of 'lists all forum channels' is reasonably implied. It is complete for its simplicity.

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?

The schema has no description for guildId, and schema coverage is 0%. The description maps the parameter to 'specified Discord server (guild)', which adds helpful context but does not explain the parameter's format or where to obtain it. Still, it provides the basic meaning needed.

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 all forum channels in a specified guild, using a specific verb ('Lists') and resource ('forum channels'). This distinguishes it from sibling tools like discord_get_channel_list (channels in general) and discord_list_forum_threads (threads within forums).

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?

The description implies when to use the tool (to list forum channels for a guild) but does not explicitly state when alternatives might be more appropriate. No exclusions or alternative tool mentions are provided, so the guidance is only implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yv3s-y4ng/mcp-discord-stream'

If you have feedback or need assistance with the MCP directory API, please join our Discord server