Cactal

View public images

webResearch_viewImage

Read-onlyIdempotent

Fetches 1 to 48 public image URLs and returns the pictures; nothing is stored. Up to 4 come back full size (an SVG also returns the start of its source); more come back on contact sheets, each a grid of pictures, each under its number (n; numbers run on across calls), with a gray checkerboard where a picture is transparent. Import the good ones with websiteAssets.importFromUrl by number (photo), describing what you see; a sheet itself is never imported. MCP clients that render images get the pictures as images; others get base64 WebP in pictures. Not billed to credits.

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": {
      "websiteId": "<websiteId>",
      "urls": "<urls>"
    },
    "name": "webResearch_viewImage"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes	Absolute public image URLs to look at: up to 4 come back full size, more come back on numbered contact sheets.
`websiteId`	Yes	A website you can edit; its organization pays for the call in AI credits.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare read-only/non-destructive, but the description adds substantial context they don't carry: images are never stored, only up to 4 are full size with the rest on numbered contact sheets, transparency appears as a gray checkerboard, rendering differs by MCP client (images vs base64 WebP in `pictures`), and the call is not billed to credits.

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?

The critical facts (what it returns, nothing stored, not billed) are front-loaded and every sentence carries operational information. The single dense paragraph packs many clauses, making the contact-sheet and import rules harder to scan than a short bulleted structure would be.

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

Completeness5/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 still covers return shape (full-size vs contact sheets, checkerboard for transparency, WebP fallback), limits, billing, and the natural next step. An agent has everything needed to call it and to act on the result.

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 both parameters are already documented, and the description largely restates the URL limits the schema gives. The extra value is the note that picture numbers run on across calls, which clarifies how returned indexes map back to inputs, but that is output-side rather than parameter semantics.

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?

States a specific verb and resource (fetches 1–48 public image URLs and returns the pictures) plus a key scope fact (nothing is stored). That scope statement alone separates it from webResearch_screenshot and websitePreview_capture, which capture pages rather than arbitrary image URLs.

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

Usage Guidelines4/5

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

Explicitly routes the follow-up action: import good images with websiteAssets.importFromUrl by number, and states the exclusion that a contact sheet itself is never imported. It does not compare against the other visual siblings (webResearch_screenshot, websitePreview_capture), so 4 rather than 5.

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

All Cactal tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?