Skip to main content
Glama

view_image

Return a workspace PNG as inline MCP image content (up to 10 MB) so clients can inspect Blender renders or saved images directly.

Instructions

Return a workspace PNG as inline MCP image content (maximum 10 MB).

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": {
      "session_id": "<session_id>",
      "path": "<path>"
    },
    "name": "view_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
session_idYes

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?

With no annotations, the description carries the full burden, and it does disclose two useful traits: the return is inline image content rather than a path or link, and there is a 10 MB ceiling. It omits error behavior for missing or oversized files, whether the read is workspace-scoped or filesystem-absolute, and whether any session permissions apply.

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?

One sentence, front-loaded with the verb and the return type, with the size cap as a trailing constraint. Nothing is wasted and nothing important is buried.

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 two-parameter read tool with no output schema, the definition covers what matters most: what comes back (inline image) and how large it can be. The remaining gap is how path and session_id interact, which the agent must guess.

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 description coverage is 0% for both required parameters, but the phrase 'workspace PNG' implicitly scopes the path to the session workspace, which is the single most important disambiguation an agent needs. The role of session_id (which session's workspace is read) is left entirely to inference.

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: returns a workspace PNG as inline MCP image content. That is clear enough to distinguish it from a generic file fetch, though it never contrasts itself with viewport_screenshot or download_file, which are the plausible confusable siblings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all. The description never says when to prefer this over viewport_screenshot (rendering the current view) or download_file (fetching bytes to disk), nor does it state any precondition such as the file already existing in the workspace.

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