Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

open_message_link

Read-only

Open a Discord message link to retrieve the linked message and surrounding context, making it easier to review or reference a specific conversation.

Instructions

Open a discord.com/channels/… message link: returns the message plus a few messages of context around it.

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": {
      "link": "<link>"
    },
    "name": "open_message_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYes
contextNoMessages of context (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds that the result includes surrounding context messages, but 'a few messages' is vague versus the documented default of 5, and nothing is said about behavior for invalid or inaccessible links.

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?

A single sentence, front-loaded with the action and the accepted input format, with the return behavior attached. No filler or redundancy.

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

Completeness3/5

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

With no output schema, the description carries the return-value burden and does so briefly. For a simple read tool it is nearly adequate, but it omits link-format edge cases and any note on failure modes when a link is unresolvable.

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 50%: 'context' is documented in the schema with its default, while 'link' has no schema description. The description partially compensates by specifying the link format (discord.com/channels/…) and mentioning context, but does not explain the context parameter's semantics itself.

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+resource — 'Open a discord.com/channels/… message link' — and adds what comes back. It implicitly distinguishes itself from ID-based retrieval siblings like get_message by requiring a URL, though it never names an alternative explicitly.

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?

The usage condition is implied by the required input: use this when you have a Discord channel message link rather than raw IDs. No explicit when-not guidance or named alternatives (e.g., get_message for ID-based lookup) are given.

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