Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

forward_message

Forward a Discord message to another channel or DM, optionally adding a comment, by supplying a message link or ID and the destination.

Instructions

Forward a message to another channel or DM (Discord's native forward).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "forward_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional text sent with the forward
messageYesMessage link, or message ID with from_channel_id
to_user_idNoOr destination user (DM)
to_channel_idNoDestination channel ID
from_channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds the meaningful behavioral nuance that this is Discord's native forward rather than a copy of text, but says nothing about permission requirements, cross-guild restrictions, or what happens when the source is inaccessible.

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?

A single front-loaded sentence with zero filler; the core action comes first and the clarifying parenthetical follows. Nothing could be removed without losing information.

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?

For a five-parameter write tool with no output schema, the description covers what the tool does and the destination alternatives. It omits error/failure behavior and the conditions under which forwarding is rejected, which an agent handling a mutation would benefit from knowing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline would be 3, but the description explicitly frames destinations as "another channel or DM," which clarifies the to_channel_id versus to_user_id choice that the schema lists only tersely. The message parameter's dual form (link or ID plus from_channel_id) is left entirely to the schema.

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?

States a specific verb and resource ("Forward a message") plus the destination scope ("another channel or DM"), and the parenthetical "Discord's native forward" distinguishes it from simply re-sending content. It stops short of naming a sibling, so an agent must infer that send_message/reply_to_message are different operations.

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?

Usage is only implied: the phrase "another channel or DM" hints at the destination choice, and "native forward" implies the original message attribution is preserved. There is no explicit when-to-use versus send_message or reply_to_message, and no stated prerequisites (e.g., needing access to both source and destination).

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

Deploy Server

Other Tools