MCP Server Discord Webhook
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISCORD_WEBHOOK_URL | Yes | Your Discord webhook URL |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageC | Discordにメッセージを送信します |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'send_message' has a clear, distinct purpose that cannot be confused with any other tool in the set.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'send_message' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
A single tool is too few for a Discord webhook server, which typically involves operations like sending messages, editing messages, deleting messages, or fetching webhook info. The scope feels incomplete with just one basic action.
The tool set is severely incomplete for a Discord webhook domain. It only provides 'send_message', missing essential operations like editing, deleting, or retrieving messages, and lacks any management functions for webhooks themselves.