Sceneplane

Apply scene operations

scene_apply

Destructive

Apply a batch of validated scene operations to a base revision. Mutating batches commit atomically into one new immutable revision (or nothing); query/select-only batches still execute in Blender and return operationResults, but create no revision and do not move the project head. Returns a durable job handle. Call docs_operations FIRST to see the vocabulary: there are 298 operations covering mesh editing, booleans, lathe/loft/sweep, curves, UV unwrap, modifiers, materials, lights, cameras, render settings, geometry nodes, and batch/query helpers — most modelling needs no scene_script at all. Prefer this over scene_script: operations are validated before dispatch and cost less.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`dryRun`	No	Validate against the ACTUAL scene and report what each operation would touch, without committing, queueing a job, or consuming compute. Free and synchronous. Resolves every id and $ref against the target revision, so stale ids, purged materials and unknown targets surface here instead of failing a whole batch, and checks material.create_node_graph sockets against the pinned Blender build; configured layouts and geometry-node graphs retain explicit advisory limits. Use it to probe an uncertain operation before spending a container on it. What it does NOT do: run any geometry, so it cannot tell you a boolean will miss, a profile will not close, or a bevel will overlap — for those, put the READ ONLY mesh.* checks in the real batch and read operationResults.
`message`	No	Short description saved with the new revision.
`projectId`	Yes	Stable project ID returned by project_create or projects_list.
`operations`	Yes	Ordered batch of validated scene operations; use docs_operations for exact schemas.
`baseRevisionId`	No	"HEAD" (default) targets the project's current head. Mutations MUST build on the head: passing an older revision is rejected with REVISION_CONFLICT, since history is linear. To continue from an older scene, revision_restore it forward first.	HEAD
`idempotencyKey`	Yes	Stable caller-chosen key for safe retries of this same request.
`generatePreview`	No	Render a thumbnail for a new revision (default maximum side 384px; previewMaxSidePx can request up to 1024px). Defaults to on for mutating batches. A batch whose operations only READ or SELECT (mesh.get_, .analyze_, mesh.select_) creates no revision, so this is forced off even when explicitly true.
`previewMaxSidePx`	No	Opt-in thumbnail maximum side in pixels; default 384, maximum 1024, preserving the active camera aspect ratio. Larger previews spend more compute at the same 16 samples. Has no effect when generatePreview is false or the batch is read-only. scene_snapshot later reads that stored image and cannot resize or regenerate it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`job`	No
`dryRun`	No
`problems`	No
`readOnly`	No
`warnings`	No
`declaredRefs`	No
`readOnlyNote`	No
`operationCount`	No
`dimensionChecks`	No
`generatePreview`	No
`geometrySimulation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

addedOutput schema / properties / dimensionChecks

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / geometrySimulation

Added value: +{
+  "const": "not_performed",
+  "type": "string"
+}

First observedSep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Discloses the atomic all-or-nothing commit into an immutable revision, the read-only no-head-move behavior, and the durable job handle, which go beyond the annotations' single destructiveHint. This gives the agent a clear side-effect model without contradicting the annotations.

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?

Three dense sentences front-load the core behavior, then add the return type and usage guidance. The list of operation categories is verbose but earns its place by establishing scope and justifying the preference over scene_script.

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?

Given a rich schema and output schema, the description covers the essentials: what it applies, revision semantics, read-only behavior, job handle, and where to learn the operation vocabulary. No critical information an agent needs to invoke it safely is missing.

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 coverage is 100%, so the description does not need to re-document parameters; the baseline is 3. It adds useful orientation by pointing to docs_operations for the operation vocabulary, but offers no per-parameter semantics beyond the schema.

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 specifically that it applies a batch of validated scene operations to a base revision, and notes atomic revision creation versus read-only execution. It also explicitly differentiates itself from scene_script ('Prefer this over scene_script'), so an agent can pick it apart from the closest sibling.

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

Usage Guidelines4/5

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

Tells the agent to call docs_operations FIRST and says to prefer scene_apply over scene_script because operations are pre-validated and cheap. It does not spell out the exact conditions under which scene_script should be used instead, but gives enough context for the common path.

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

All Sceneplane tools Inspect

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

Need Help?