Skip to main content
Glama
Sign In
mcp-discord-bridge

mcp-discord-bridge

by iprashantraj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_message

Send a message to a specified Discord text channel by providing the channel ID and text content.

Instructions

Send a message to a Discord text 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

NameRequiredDescriptionDefault
channel_idYes
contentYesThe message text to send (max 2000 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as permission requirements, rate limits, or error handling. It only states the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is too minimal. It lacks structure and could include more detail while remaining concise.

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 the number of related sibling tools and the absence of an output schema, the description is incomplete. It does not specify return values, prerequisites, or how this tool differs from similar ones.

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 50% (only content has a description). The tool description does not add any meaning beyond the schema, such as explaining how to obtain channel_id.

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 states the specific action (send) and resource (message to a Discord text channel). However, it does not differentiate from sibling tools like send_dm or send_webhook_message, which have similar purposes.

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?

No guidance on when to use this tool versus alternatives like send_dm or reply_to_forum_post. The agent is left to infer context from the name.

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