Skip to main content
Glama

Preview a TOP

get_preview
Read-only

Capture a TOP node's current output as an inline PNG image for visual inspection, or get a lightweight RGBA sample grid as JSON for a cheaper status check.

Instructions

Capture a TOP node's current output as an inline PNG image so you can see what was created — read-only, it creates and modifies nothing. Returns the image (scaled to width×height) plus a caption with the node path and actual dimensions; only TOPs can be previewed (CHOP/SOP/etc. have no image). For a much cheaper check (is it alive / roughly what colour?) pass sample_grid=N to get an N×N grid of RGBA samples + per-channel stats as JSON instead of an image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNoWidth of the captured preview image in pixels (1–4096; default 640).
heightNoHeight of the captured preview image in pixels (1–4096; default 360).
job_idNoCollect a previously deferred capture (from a delay_frames call) by its job_id.
node_pathNoPath of the TOP node to capture. Required unless collecting a deferred job by job_id.
pre_pulsesNoParameters to pulse in the SAME frame immediately before capturing — e.g. reset a feedback loop or fire a timer so a transient is actually visible. All targets are validated before any fires (all-or-nothing).
sample_gridNoWhen set (2–16), return a lightweight N×N grid of RGBA samples + per-channel min/max/mean as JSON instead of an image — 10–50× cheaper. Use this when you only need to know whether the output is alive / roughly what colour it is, not its spatial detail.
delay_framesNoDefer the capture by N frames (to catch an event that appears a few frames after a pulse). Returns a job_id + wait_ms instead of the image; call get_preview again with that job_id to collect the result.
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces 'read-only, creates and modifies nothing'. It adds that only TOPs have images, that the image is scaled, and that sample_grid returns JSON. No contradiction.

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?

The description is concise, with the main purpose in the first sentence, followed by return details and the alternative sampling mode. Every sentence adds value, no fluff.

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?

Despite no output schema, the description explains the return format (image with caption, or JSON with stats). It covers all major behaviors (preview, sample, deferral, pre-pulses) and constraints (only TOPs). Complete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning: sample_grid is '10–50× cheaper' and returns per-channel stats; delay_frames returns job_id and wait_ms; pre_pulses explains all-or-nothing validation. These details greatly aid agent understanding.

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 clearly states the tool captures a TOP node's output as a PNG image. It distinguishes itself from siblings by specifying it only works with TOPs and provides an alternative sampling mode. The verb 'capture' and resource 'TOP node output' are specific.

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?

The description explicitly tells when to use the sample_grid alternative (for cheap checks) and when not to use (non-TOP nodes). It also explains deferral with delay_frames and collection via job_id, providing clear guidance on different use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server