Skip to main content
Glama
jar285

MCP-Discord

by jar285

discord_reply_to_forum

Add a reply to an existing Discord forum 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 main execution logic for the 'discord_reply_to_forum' tool. Fetches the specified thread by ID, validates it supports sending messages, and sends the provided message as a reply.
    case "discord_reply_to_forum": {
      const { threadId, message } = ReplyToForumSchema.parse(args);
      try {
        if (!client.isReady()) {
          return {
            content: [{ type: "text", text: "Discord client not logged in. Please use discord_login tool first." }],
            isError: true
          };
        }
    
        const thread = await client.channels.fetch(threadId);
        if (!thread || !(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 {
          content: [{ type: "text", text: `Failed to reply to forum post: ${error}` }],
          isError: true
        };
      }
    }
  • Zod input validation schema for the tool, defining required string parameters 'threadId' and 'message'.
    const ReplyToForumSchema = z.object({
        threadId: z.string(),
        message: z.string()
    });
  • src/index.ts:266-277 (registration)
    Tool registration in the MCP server's tool list, providing name, description, and JSON schema for inputs.
    {
      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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Adds a reply') which implies a write operation, but doesn't mention permission requirements, rate limits, whether replies are editable/deletable, or what happens on success/failure. This leaves significant gaps for a mutation tool.

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 tool with two parameters and no complex behavior described.

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 no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It covers the basic action but lacks critical context about permissions, error conditions, return values, and parameter details needed for reliable tool invocation.

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?

With 0% schema description coverage for both parameters, the description adds no semantic information about what 'threadId' or 'message' represent. It doesn't explain threadId format (e.g., Discord snowflake), message constraints (length, formatting), or provide examples. The description fails to compensate for the complete lack of schema documentation.

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. However, it doesn't differentiate from sibling tools like 'discord_send' or 'discord_send_webhook_message' which might also send messages in different contexts.

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 (like needing an existing thread), when not to use it (e.g., for initial posts), or refer to sibling tools like 'discord_create_forum_post' for creating new posts versus replying to existing ones.

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

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