Skip to main content
Glama

Canvas Capture View

aimixer_canvas_capture_view
Read-onlyIdempotent

Use when you need a screenshot of an OPEN Canvas exactly as the user sees it, including graph, node thumbnails, viewport and live UI. This asks the live authenticated page for one real PNG (no synthetic renderer, no billing). target=viewport uses its current camera, fit shows the entire graph; rect/point/nodes focus a region. Returns an ImageContent PNG and small layout/loading metadata. Requires an open visible Canvas page; if unavailable use aimixer_canvas_view_session, for individual images use inspect_images.

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>"
    },
    "name": "aimixer_canvas_capture_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
rectNo
targetNo
node_idsNo
project_idYes
instance_idNo
max_edge_pxNo
expected_revNo

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.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses that the capture comes from the live authenticated page, produces a real PNG, and incurs no billing — meaningful operational context. The remaining gap is the failure mode when the page is loading or hidden, which is only partially covered by the 'small layout/loading metadata' note.

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 use condition, then behavior, then targeting modes, then routing — a logical order with no filler sentences. It is dense but all four sentences carry information; the target-mode sentence is a little compressed, but nothing is redundant.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the nature of the return value (ImageContent PNG plus metadata) and the precondition, which is the most important context, and an output schema exists so return shape needn't be restated. However, for a 9-parameter tool with a nested rect object and zero schema coverage, the unexplained parameters (max_edge_px, expected_rev, instance_id, node_ids) leave real gaps.

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 carries the burden, and it only explains the target enum values (viewport uses current camera, fit shows the whole graph, rect/point/nodes focus a region). It adds nothing about node_ids, x/y pairing, max_edge_px, expected_rev, or instance_id, leaving several parameters undocumented in both places.

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 (capture a screenshot of an open Canvas) plus the defining scope: 'exactly as the user sees it, including graph, node thumbnails, viewport and live UI.' It also distinguishes itself from a synthetic rendering path ('no synthetic renderer'), which separates it from the static snapshot/preview siblings without naming them.

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?

Gives an explicit when-to-use ('Use when you need a screenshot of an OPEN Canvas') and a when-not precondition ('Requires an open visible Canvas page') with a named fallback, aimixer_canvas_view_session, plus a second alternative, inspect_images, for single images. Routing is unambiguous.

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