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

discord-admin-mcp

by pedroaop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

send_message

Send a message to a Discord channel as the bot. Use it to post content or automated notifications through the Discord REST API.

Instructions

Envia mensagem num canal como o bot.

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
contentYes
channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it only discloses that the message is authored by the bot. It says nothing about required permissions, rate limiting, whether mentions/pings are triggered, or what the call returns.

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?

A single front-loaded sentence with zero filler, which is structurally clean. However, the brevity crosses into under-specification for a write operation rather than reflecting disciplined concision.

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?

This is an unannotated mutation tool with no output schema and 0% parameter coverage, so the description was the only place to convey permissions, side effects, and return shape. It supplies one useful fact (bot authorship) but leaves the rest to guesswork.

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 0%, so both parameters arrive with only a title. The description weakly maps "canal" to channel_id and "mensagem" to content, but adds no format constraints such as accepted ID syntax, content length limits, or markdown support.

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 a specific verb and resource ("Envia mensagem num canal") and adds the actor identity ("como o bot"), which meaningfully distinguishes it from siblings like read_messages or delete_message. It stops short of naming which sibling to use instead, but the core action is unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as delete_message or read_messages. An agent can infer this is the write counterpart to reading a channel, but nothing in the text confirms that.

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