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

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_send_file

Send a file or image to a Discord channel using a data URI or HTTP URL. Supports optional message text and multiple file uploads.

Instructions

Send a file/image to a channel. source is a data URI or http(s) URL. For multiple files use the files array.

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": {
      "channelId": "<channelId>"
    },
    "name": "discord_send_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNo
sourceNodata URI or http(s) URL of the file
contentNoOptional message text
filenameNo
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It mentions source format (data URI or http(s) URL) and multiple file support, but omits details like permissions, file size limits, side effects, or return value. It provides basic but not comprehensive transparency.

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 exceptionally concise, with two sentences that deliver the core purpose and key parameter guidance immediately. No unnecessary words.

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 five parameters and no output schema, the description covers the essential distinction (single vs multiple files) but leaves other parameters like filename and content largely unexplained. It is adequate for basic usage but not exhaustive.

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?

The description adds meaning beyond the schema by clarifying that source is a data URI or http(s) URL and that for multiple files one should use the files array. This explains the relationship between source and files, which the schema alone does not. However, filename and content remain poorly explained.

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 clearly states the tool sends a file/image to a channel, distinguishing it from text message or embed tools. It also mentions the files array for multiple files, which adds specificity.

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 limited guidance: it notes using the files array for multiple files, but fails to specify when to choose this tool over alternatives like discord_send_message or discord_send_embed. No exclusions or context for selection.

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