Discord MCP

by RestartFU

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_message

Read-only

Retrieve a single Discord message by providing the channel ID and message ID.

Instructions

Read one message.

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>",
      "message_id": "<message_id>"
    },
    "name": "get_message"
  }
}

Input Schema

Name	Required	Description	Default
`channel_id`	Yes
`message_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the singular granularity but does not describe other behavioral aspects such as error responses, missing-message handling, or return format. This is acceptable but not rich.

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 three words with no filler, front-loaded, and every word contributes meaning. It is concise without sacrificing core clarity.

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 simple read operation with strong read-only annotations and a clear required-parameter schema, the description is mostly complete. It could be improved by mentioning that a single message object is returned and by distinguishing usage from read_messages, but these are minor gaps given the tool's simplicity.

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%, and the description does not mention channel_id or message_id at all. The parameter names are self-explanatory, but the description fails to compensate for the lack of schema descriptions or clarify how the IDs relate to the operation.

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 'Read one message' uses a specific verb and resource, clearly identifying a single-message retrieval operation. It distinguishes itself from plural/sibling tools like read_messages by emphasizing 'one' message.

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

Usage Guidelines3/5

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

Usage context is implied: use this tool when you need a single message identified by channel and message IDs. However, it does not explicitly state when to prefer read_messages or search_messages instead, nor does it mention any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.