Skip to main content
Glama

discord_reply_to_forum

Adds a reply to an existing Discord forum post or thread by providing the thread ID and message content.

Instructions

Adds a reply to an existing forum post or thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadIdYes
messageYes

Implementation Reference

  • The replyToForumHandler function that executes the discord_reply_to_forum tool logic. It fetches a thread, validates it supports sending messages, and sends the reply.
    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);
      }
    };
  • ReplyToForumSchema Zod schema defining input validation: threadId (string) and message (string), both required.
    export const ReplyToForumSchema = z.object({
      threadId: z.string(),
      message: z.string(),
    });
  • src/server.ts:128-131 (registration)
    Registration of discord_reply_to_forum in the MCP server's CallToolRequestSchema handler, routing to replyToForumHandler.
    case 'discord_reply_to_forum':
      this.logClientState('before discord_reply_to_forum handler');
      toolResponse = await replyToForumHandler(args, this.toolContext);
      return toolResponse;
  • Tool definition/registration in the tool list with name, description, and input schema for discord_reply_to_forum.
    {
      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'],
      },
    },
Behavior2/5

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

No annotations provided, and the description only states the action without disclosing behavioral traits like permissions required, error handling, or idempotency. Relies entirely on the minimal description.

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?

Single sentence, no extraneous information. Efficiently communicates the core function.

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 absence of annotations and output schema, the description provides minimal context. It does not explain return values or error states, but for a simple tool the basic action may suffice. Gaps remain.

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 has 0% description coverage. The description hints that 'threadId' is the target and 'message' is the reply content, adding some context beyond the bare schema. However, it lacks detail on format or constraints.

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?

Description clearly states the action ('Adds a reply') and the target ('existing forum post or thread'). Distinguishes from siblings like 'discord_create_forum_post' (creates new) and 'discord_send' (sends to channel).

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?

Implies usage for replying to existing forums/threads, but provides no explicit when-to-use or when-not-to-use guidance. No alternatives mentioned despite siblings existing.

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