Skip to main content
Glama

Canvas Inspect Images

aimixer_canvas_inspect_images
Read-onlyIdempotent

Use when you need to see photos, references or image GEN results (output_index). Return the actual pixels of up to 8 image nodes of an owned Canvas project as MCP image blocks: media photo nodes and finished image GEN results (output_index). Resized to max_edge_px, EXIF-oriented, JPEG or PNG when transparent. Account-owned managed media only, no remote fetch, no AI vision, no billing. Video nodes: use aimixer_canvas_inspect_media.

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": {
      "project_id": "<project_id>",
      "node_ids": "<node_ids>"
    },
    "name": "aimixer_canvas_inspect_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idsYes
project_idYes
max_edge_pxNo
output_indexNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, but the description adds substantive behavior beyond them: resizing to max_edge_px, EXIF orientation normalization, JPEG output with PNG only when transparency is needed, and account-owned managed media only with no remote fetch, no AI vision, and no billing. These constraints materially affect whether an agent can call the tool successfully.

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 trigger condition is front-loaded and the alternative-tool routing is last, which is good structure, and most sentences carry distinct constraints. It loses a point for redundancy: 'image GEN results (output_index)' and 'media photo nodes' each appear twice in the first two sentences.

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 an output schema present, return-value shape need not be described, and the definition covers input constraints, ownership requirements, format behavior, and the video alternative. The remaining gap is the unexplained semantics of output_index and the absence of defaults for max_edge_px, which are the only things an agent would still guess at.

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 description coverage is 0%, so the description must carry the load; it partially does by tying 'up to 8 image nodes' to the maxItems cap, 'Resized to max_edge_px' to that parameter, and 'image GEN results (output_index)' to the output selector. However, it never explains what output_index means semantically (which output of a GEN node), gives no defaults or ranges for max_edge_px (256-1536), and says nothing about node_ids format or that project_id identifies the owned Canvas.

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?

The description states a specific verb and resource ('Return the actual pixels of up to 8 image nodes of an owned Canvas project as MCP image blocks') together with the scope limits. It also names the sibling it is not for ('Video nodes: use aimixer_canvas_inspect_media'), so an agent can route without inspecting either schema.

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

Usage Guidelines5/5

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

It opens with an explicit when-to-use clause ('Use when you need to see photos, references or image GEN results') and closes with an explicit exclusion plus the alternative tool for video nodes. Both the positive trigger and the negative case are stated, not inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources