Skip to main content
Glama

discord_reply_to_forum

Post responses to Discord forum threads by providing a thread ID and message content for AI assistants to participate in discussions.

Instructions

Adds a reply to an existing forum post or thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadIdYes
messageYes

Implementation Reference

  • The primary handler function that executes the discord_reply_to_forum tool: validates input, fetches the forum thread, checks permissions, sends the reply message, and returns success or error.
    export const replyToForumHandler: ToolHandler = async (args, { client }) => {
      const { threadId, message } = ReplyToForumSchema.parse(args);
    
      try {
        if (!client.isReady()) {
          return {
            content: [{ type: 'text', text: 'Discord client not logged in.' }],
            isError: true,
          };
        }
    
        const thread = await client.channels.fetch(threadId);
        if (!thread?.isThread()) {
          return {
            content: [
              { type: 'text', text: `Cannot find thread with ID: ${threadId}` },
            ],
            isError: true,
          };
        }
    
        if (!('send' in thread)) {
          return {
            content: [
              {
                type: 'text',
                text: 'This thread does not support sending messages',
              },
            ],
            isError: true,
          };
        }
    
        // Send the reply
        const sentMessage = await thread.send(message);
    
        return {
          content: [
            {
              type: 'text',
              text: `Successfully replied to forum post. Message ID: ${sentMessage.id}`,
            },
          ],
        };
      } catch (error) {
        return handleDiscordError(error);
      }
    };
  • MCP tool definition including name, description, and input schema (threadId and message required).
    {
      name: 'discord_reply_to_forum',
      description: 'Adds a reply to an existing forum post or thread',
      inputSchema: {
        type: 'object',
        properties: {
          threadId: { type: 'string' },
          message: { type: 'string' },
        },
        required: ['threadId', 'message'],
      },
    },
  • src/server.ts:128-131 (registration)
    Registration and dispatch in the MCP server's tool call handler switch statement, invoking the replyToForumHandler.
    case 'discord_reply_to_forum':
      this.logClientState('before discord_reply_to_forum handler');
      toolResponse = await replyToForumHandler(args, this.toolContext);
      return toolResponse;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is an 'add' operation, implying creation/mutation, but doesn't cover permissions needed, rate limits, whether replies are editable/deletable, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple tool and front-loads the core functionality without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It covers the basic purpose but misses parameter details, behavioral context, usage guidance, and expected outcomes. The agent would struggle to use this effectively without external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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 but adds no parameter information. It doesn't explain what threadId represents (e.g., Discord thread ID format), what message content is allowed (e.g., markdown, attachments), or any constraints. The two required parameters remain entirely undocumented beyond their schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Adds a reply') and target resource ('to an existing forum post or thread'), making the purpose immediately understandable. It distinguishes from siblings like discord_create_forum_post (which creates new posts) and discord_send (which sends messages to channels). However, it doesn't specify the exact forum context, leaving some ambiguity about where this applies.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing thread), when not to use it (e.g., for direct messages vs forum posts), or how it differs from similar tools like discord_send. The agent must infer usage from the name and context alone.

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/IQAIcom/mcp-discord'

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