Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get one message

get_message
Read-onlyIdempotent

Fetch a single Discord message by ID or link to inspect its attachments, embeds, reactions, and replied-to message; optionally scan newer messages for replies.

Instructions

Fetches one message by ID or link, with attachments (IDs, sizes, URLs), embeds, reactions and the message it replies to. include_replies: true also scans later messages for replies to it and says how many it scanned.

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

Input Schema

NameRequiredDescriptionDefault
userNoInstead of channel: a user (ID, <@mention> or name) whose DM channel to use.
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
channelNoChannel or thread: ID, <#mention>, link, or name. Archived threads by ID or link.
messageYesMessage ID or message link (https://discord.com/channels/...). With a link, channel is optional.
scan_limitNoMax newer messages to scan for replies (default 500).
include_repliesNoAlso find replies to this message (scans newer messages).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the bar is lower, yet the description still adds value: it discloses the exact return payload and the non-obvious side effect that include_replies scans newer messages and reports how many were scanned. It does not mention failure modes (missing message, missing permissions), which keeps it from a 5.

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?

Two dense sentences, front-loaded with the primary purpose and payload, followed by the one optional behavior that changes results. No filler or redundant restatement of the title.

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 read-only single-entity fetch with no output schema, the description covers purpose, returned fields, and the reply-scanning option — enough to call it correctly. Only error/not-found behavior and the scan_limit interaction (default 500, max 10000) are left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by clarifying that the message can be an ID or a link and that include_replies triggers a scan whose extent is reported. It wisely defers the user/guild/channel/scan_limit semantics to the schema rather than restating them.

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?

States a specific verb and resource ('Fetches one message by ID or link') and enumerates the payload it returns (attachments, embeds, reactions, referenced message), which distinguishes it from bulk siblings like read_messages or search_messages. It does not name an alternative explicitly, so it stops short of a 5.

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 is implied by 'by ID or link' and by the include_replies/scan_limit behavior, giving an agent enough to know this is a single-message lookup. There is no explicit when-to-use-vs-alternative guidance or stated preconditions (e.g., when to prefer get_new_messages or search_messages).

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