Skip to main content
Glama
Sign In
nuke-mcp

nuke-mcp

by hramirezedc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

preview_frame

Read-only

Renders one frame from any Nuke node to an image and returns it, using a temporary Write node that is removed afterward. Set max_size to scale the longest side down.

Instructions

Look at the output of any node: renders one frame to an image and returns it.

Uses a temporary Write node (removed afterwards). `max_size` is the longest-side width in pixels the image is scaled down to.

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": {
      "node": "<node>"
    },
    "name": "preview_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoauto
nodeYes
frameNo
formatNojpg
scriptNo
max_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Goes beyond the supplied annotations by disclosing the mechanism: it creates a temporary Write node and removes it afterwards, so the agent knows a transient mutation occurs despite readOnlyHint=true. It also explains the downscaling behavior of `max_size`, though it says nothing about latency or output image handling.

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?

Three short sentences, front-loaded with the core action and its return value. The temporary-Write-node detail earns its place as non-obvious behavior; no filler.

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

Completeness2/5

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

With six parameters, 0% schema description coverage, and no output schema, the description is too thin: an agent cannot tell what `mode`, `frame`, or `script` do or how the returned image is delivered. Only one of six parameters is covered.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the description must carry the load, and it only defines `max_size`. The meaning of `mode` (auto/live/headless), `frame` (null default), `format`, and `script` is left entirely unexplained.

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?

"Renders one frame to an image and returns it" names a specific verb (render), resource (a node's output frame), and result (image returned). The single-frame scope implicitly separates it from the sibling `render`, though that alternative is never named.

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

Usage Guidelines3/5

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

"Look at the output of any node" hints at the use case (quick visual inspection) but gives no explicit when-to-use/when-not guidance and never mentions the `render` sibling or what distinguishes a single-frame preview from a full render.

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

Deploy Server

Other Tools