@striderlabs/mcp-discord

send_message

Send a message to a Discord channel using its channel ID. Reply to an existing message to add context.

Instructions

Send a message to a Discord channel

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": {
      "channel_id": "<channel_id>",
      "content": "<content>"
    },
    "name": "send_message"
  }
}

Input Schema

Name	Required	Description
`content`	Yes	The message content to send
`channel_id`	Yes	The Discord channel ID to send the message to
`reply_to_message_id`	No	Optional: message ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It only states that a message is sent and does not disclose side effects, permission requirements, rate limits, delivery guarantees, or return behavior, which are important 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 concise sentence with no filler. It is front-loaded with the action and resource, making it easy to scan and understand.

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?

Given no annotations, no output schema, and a write operation, the description is thin. It tells the agent what the tool does but not when to prefer it, what to expect after invocation, or what constraints apply, so context is incomplete.

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 description coverage is 100%, so the parameters are already well documented. The description adds no extra detail about parameter semantics, but also does not need to compensate much beyond the schema.

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 uses a specific verb ('Send') and resource ('a message to a Discord channel'), making the tool's purpose immediately clear. It also distinguishes this from the sibling read/search tools such as get_messages, get_dms, and search_messages.

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 intended use is implied by the word 'send' rather than explicitly contrasted with the get/search siblings. There is no stated when-to-use or when-not-to-use guidance, but the description makes it understandable that this is the tool for posting a message.

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

Deploy Server