Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

view_image

Read-only

Fetch and display an image from a Discord message attachment (message link/ID plus optional index) or any image URL for visual inspection.

Instructions

Look at an image: a message attachment (message link/ID + optional index) or any image URL. Returns the image itself.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "view_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
indexNoAttachment index (default 0)
messageNo
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior in 'Returns the image itself', telling the agent it yields image content rather than metadata or a text link. It stops short of noting auth requirements, fetch failures, size limits, or whether index 0 is assumed when omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the core action and the source variants. No filler, though the packed parenthetical makes the parameter pairing slightly denser than it needs to be.

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?

For a 4-parameter, zero-required-parameter tool with no output schema, the description correctly spends its words on the return shape ('the image itself') and the source modes. However, with only 25% schema coverage, the omission of channel_id semantics and the url-vs-message exclusivity rule leaves an agent guessing at invocation details.

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 only 25% (only 'index' is documented), so the description must carry weight; it does explain that 'message' accepts a link or ID and that 'index' is optional and attachment-scoped, and that 'url' takes any image URL. The fourth parameter, channel_id, is never mentioned, and how channel_id pairs with a bare message ID versus a full message link is left unclear.

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?

Uses a concrete verb ('Look at') with a clear resource ('an image') and explicitly names the two supported sources: a message attachment via message link/ID plus optional index, or any image URL. It is unmistakable what the tool does, though it does not compare itself to any sibling (none of the listed siblings appear to overlap).

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 two modes imply when to use it — viewing an attachment from a message vs. fetching an arbitrary image URL — but there is no explicit guidance on mutual exclusivity of parameters (url vs. message/channel_id) or what to do when an attachment index is out of range. Usage is implied rather than spelled out.

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