Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Send a message

send_message

Sends messages to Discord channels, threads, forum posts, or DMs with replies, embeds, file attachments, and controlled @everyone mentions, returning the message ID and link.

Instructions

Sends a message to a channel, thread, forum post or a user's DMs (pass "user"). Supports replies, up to 10 embeds and 10 file attachments (local path in stdio mode, https URL, or base64). Content max 2000 characters. @everyone/@here only ping if mention_everyone is true. Returns the new message ID and link. To start a new forum post, use create_thread.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoInstead of channel: a user (ID, <@mention> or name) whose DM channel to use.
filesNoUp to 10 attachments.
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
embedsNoUp to 10 rich embeds.
silentNoSend without push notifications.
channelNoChannel or thread: ID, <#mention>, link, or name. Archived threads by ID or link.
contentNoMessage text (Discord markdown, max 2000 characters).
reply_toNoMessage ID or link to reply to (same channel).
mention_everyoneNoAllow @everyone/@here to ping (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish a non-read-only, non-idempotent, open-world write, and the description adds real value beyond them: the 2000-character cap, the 10-embed/10-file limits, the three file-source modes, the mention gating rule, and the return value. It does not mention rate limiting or retry/duplicate-send risk, which matters given idempotentHint=false.

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?

Five tight sentences, front-loaded with the primary action and targets, then limits, then return value, then the sibling redirect. No filler or redundancy that isn't functional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter open-world write with no output schema, the description covers targets, size caps, attachment modes, mention semantics, return values, and the create_thread alternative. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so every parameter is already documented in the schema. The description adds only marginal meaning, chiefly the 'pass "user"' routing hint and reiterating the 2000-character content cap; it does not explain interactions between channel/user or reply_to constraints beyond what the schema states.

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?

States a specific verb and resource ('Sends a message') plus the full target set: channel, thread, forum post, or a user's DMs via the 'user' parameter. It also names the sibling it is not for new forum posts ('use create_thread'), so an agent can distinguish it without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear situational routing: pass 'user' for DMs, use create_thread to start a new forum post, and note that @everyone/@here only ping when mention_everyone is true. It stops short of explicit when-not guidance against siblings like edit_message or reply workflows via reply_to.

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