Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Schedule message

schedule_message

Post a Discord message at a later time, once or on a daily or weekly repeat. Set the channel, content, and ISO send time so the server delivers it when due.

Instructions

Post a text message to a channel at a later time, once or on a daily or weekly repeat. This sends an ordinary message; for a community event members can RSVP to, use create_event. This server sends it when the time comes. One limit worth knowing: delivery needs this server to be running at that moment, so always-on scheduling wants the hosted or Docker deployment rather than a laptop that sleeps. A message that came due during downtime is sent at the next start.

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": "<channel>",
      "content": "<content>",
      "send_at": "<send_at>"
    },
    "name": "schedule_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
repeatNoDefault none.
channelYesChannel name or ID.
contentYes
send_atYesWhen to send, ISO time like 2026-07-01T17:00:00Z.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, which only mark it non-read-only and non-destructive, the description discloses the critical operational constraint: the server must be running at delivery time, and missed messages are sent at the next start. It also explains repeat behavior and recommends hosted/Docker deployment for always-on scheduling, which is rich behavioral context.

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 front-loaded: it states the action, names the sibling alternative, then explains the delivery caveat. The five sentences are clear and every one contributes to safe use; there is little wasted wording.

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

Completeness4/5

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

For a scheduling tool with minimal annotations and no output schema, the description covers purpose, alternatives, repeat behavior, and the key downtime caveat. It is slightly incomplete because it does not say what a successful call returns or how to cancel/manage a scheduled message, though those gaps are minor.

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 80%, so the schema already documents guild, repeat, channel, and send_at. The description adds broad semantics ('ordinary message', 'once or daily or weekly', 'at a later time') but does not explain the guild default, the relationship between repeat and send_at, or the content length limit beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource ('Post a text message to a channel') plus the scheduling scope ('at a later time, once or on a daily or weekly repeat'). It also explicitly distinguishes this from create_event for RSVP events, so an agent can identify it against siblings without opening the 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?

It gives a clear use case (future delivery) and an explicit when-not/alternative for community events ('use create_event'). The main gap is that it does not name send_message for immediate posting or cancel_scheduled_message for management, so the agent must infer the most common sibling boundary.

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