Skip to main content
Glama
Sign In

Mixer AI

by io.github.y110692
OverviewDiscussionsAdmin

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context the annotations cannot: resize ceiling, EXIF orientation normalization, format selection (JPEG or PNG when transparent), the 8-node batch cap, and hard scope limits (account-owned managed media only, no remote fetch, no AI vision, no billing). Those exclusions directly shape whether the agent should call this at all.

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?

Front-loaded with the trigger and the core capability, and nearly every clause carries information. Minor redundancy: "output_index" and "image nodes / image GEN results" are each restated, costing a little density.

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?

There is no output schema, so the description's "MCP image blocks" note usefully fills that gap, and the scope limits cover the safety-critical unknowns. Edge behavior — mixed valid/invalid node_ids, partial failures, or what output_index does when a node has a single output — is left unstated.

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?

With 0% schema description coverage the description must carry the load, and it does map all four params to behavior: node_ids capped at 8 image nodes, project_id scoped to "owned Canvas project", max_edge_px driving resize, and output_index for GEN results. It stops short of clarifying what output_index means for multi-output nodes or the 256–1536 bounds on max_edge_px.

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 — "Return the actual pixels of up to 8 image nodes" — plus the return format (MCP image blocks). It also explicitly distinguishes itself from the video-oriented sibling aimixer_canvas_inspect_media, so an agent can route correctly without opening the 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?

Opens with an explicit trigger ("Use when you need to see photos, references or image GEN results") and names the alternative for the excluded case ("Video nodes: use aimixer_canvas_inspect_media"). Both the when and the when-not are stated outright.

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

All Mixer AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources