Skip to main content
Glama

view_image

Read-only

Retrieves an image from a message, URL, local path, or file ID and returns it for inspection.

Instructions

Look at a picture: pass a message_id (first image in that message), an image URL, a local path, or an image file id. Returns the image so you can see it.

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
urlNoImage URL / path / base64
fileNoImage file id from a message segment (get_image)
indexNoWhich image in the message (0-based)
message_idNoMessage containing the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the key behavioral fact beyond annotations: the return value is the image itself rendered for visual inspection, not a path or metadata. It omits format/size limits and what happens when a message contains no image.

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 clauses with the input-selection modes front-loaded and the return behavior last. Every element earns its place, though cramming four input modes into one parenthetical makes it slightly dense on first read.

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?

With no output schema, the description correctly spends its words on what comes back (the image itself). For a four-parameter read tool with full annotation coverage, the only real gap is failure behavior when the message or URL has no usable image.

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 100%, so every parameter is already documented, including url accepting URL/path/base64 and file being an id from get_image. The description mostly restates these, adding only that a message_id yields the first image (which merely echoes index's default of 0). Baseline 3 applies when the schema does the heavy lifting.

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 names a concrete verb and resource ("Look at a picture") and enumerates the four ways to designate the image, which separates it from metadata tools like get_image and text extractors like ocr_image. It does not explicitly name a sibling, so the differentiation is implied rather than stated.

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: call this when you actually need to see the image. It cross-references get_image as the source of file ids, which is genuinely helpful. However, it never states when NOT to use it (e.g., prefer ocr_image for text extraction or download_file_image_stream for raw bytes), so the agent must infer the boundary.

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