Sceneplane

Generate PBR maps from an image

material_from_image

Turn ONE uploaded image (e.g. a logo PNG) into a full PBR material — deterministic, no AI. A mask (alpha channel, or bright/dark regions) drives derived roughness (baseRoughness/maskRoughness), embossed normal + height maps, optional metallic, and a base color composited over baseColor. Commits a new revision with the material (applyToObjects assigns it); maps pack into the .blend. Generated maps cap at 2048px on the longest edge — for full-resolution label/print work (4K macro shots), embed the original texture in a GLB and import via asset_import. Flow: upload_create → PUT → upload_complete → material_from_image. Returns a durable job handle. Explicit profile=surface/decal/supplied opts into the version-2 downloadable map workflow with roles and options; legacy mask/emboss arguments apply only when profile is omitted. Decals preserve transparency without implicit relief or metallic.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`roles`	No
`emboss`	No
`assetId`	Yes
`options`	No
`profile`	No
`baseColor`	No
`projectId`	Yes	Stable project ID returned by project_create or projects_list.
`maskSource`	No		alpha
`baseMetallic`	No
`maskMetallic`	No
`materialName`	No		Image Material
`baseRoughness`	No
`maskRoughness`	No
`applyToObjects`	No
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`job`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 27, 2026

addedInput schema / properties / baseColor / items

Added value: +{
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / baseColor / maxItems
```
Added value: +4
```
addedInput schema / properties / baseColor / minItems
```
Added value: +4
```

removedInput schema / properties / baseColor / prefixItems

Removed value: -[
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  }
-]

addedInput schema / properties / options / properties / roughnessRange / items
```
Added value: +{
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / options / properties / roughnessRange / maxItems
```
Added value: +2
```
addedInput schema / properties / options / properties / roughnessRange / minItems
```
Added value: +2
```

removedInput schema / properties / options / properties / roughnessRange / prefixItems

Removed value: -[
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  }
-]

Changed3 schema fields changedSep 27, 2026

addedInput schema / properties / options

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "alphaCutoff": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "alphaMode": {
+      "enum": [
+        "opaque",
+        "mask",
+        "blend"
+      ],
+      "type": "string"
+    },
+    "displacementMode": {
+      "enum": [
+        "none",
+        "bump",
+        "displacement"
+      ],
+      "type": "string"
+    },
+    "emissionStrength": {
+      "maximum": 10000,
+      "minimum": 0,
+      "type": "number"
+    },
+    "heightMidlevel": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "heightScale": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "heightSource": {
+      "enum": [
+        "none",
+        "luminance",
+        "alpha"
+      ],
+      "type": "string"
+    },
+    "maxSize": {
+      "maximum": 4096,
+      "minimum": 8,
+      "type": "integer"
+    },
+    "metallic": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "normalConvention": {
+      "enum": [
+        "opengl",
+        "directx"
+      ],
+      "type": "string"
+    },
+    "normalStrength": {
+      "maximum": 16,
+      "minimum": 0,
+      "type": "number"
+    },
+    "outputNormalConvention": {
+      "enum": [
+        "opengl",
+        "directx"
+      ],
+      "type": "string"
+    },
+    "packing": {
+      "enum": [
+        "none",
+        "orm"
+      ],
+      "type": "string"
+    },
+    "physicalCoverageMeters": {
+      "additionalProperties": false,
+      "properties": {
+        "height": {
+          "exclusiveMinimum": 0,
+          "maximum": 100000,
+          "type": "number"
+        },
+        "width": {
+          "exclusiveMinimum": 0,
+          "maximum": 100000,
+          "type": "number"
+        }
+      },
+      "required": [
+        "width",
+        "height"
+      ],
+      "type": "object"
+    },
+    "roughness": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "roughnessMode": {
+      "enum": [
+        "constant",
+        "luminance",
+        "inverted_luminance"
+      ],
+      "type": "string"
+    },
+    "roughnessRange": {
+      "prefixItems": [
+        {
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        },
+        {
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        }
+      ],
+      "type": "array"
+    },
+    "seamMode": {
+      "enum": [
+        "analyze",
+        "blend"
+      ],
+      "type": "string"
+    },
+    "specular": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "tile": {
+      "enum": [
+        "none",
+        "x",
+        "y",
+        "xy"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / profile

Added value: +{
+  "enum": [
+    "surface",
+    "decal",
+    "supplied"
+  ],
+  "type": "string"
+}

addedInput schema / properties / roles

Added value: +{
+  "items": {
+    "enum": [
+      "base_color",
+      "normal",
+      "height",
+      "roughness",
+      "metallic",
+      "opacity",
+      "emission",
+      "ao",
+      "specular",
+      "specular_color",
+      "gloss",
+      "cavity",
+      "diffuse"
+    ],
+    "type": "string"
+  },
+  "maxItems": 13,
+  "minItems": 1,
+  "type": "array"
+}

First observedSep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare the mutation/safety profile, yet the description adds substantial non-obvious behavior: deterministic processing, a committed new revision, a durable async job handle, a 2048px cap on generated maps, and profile-gated argument semantics. None of this is recoverable from the annotations or schema. No contradiction with idempotentHint=false — the idempotencyKey is a caller-supplied retry guard, not a tool-level idempotency claim.

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-loads the core purpose before the pipeline and profile branching, and every clause carries information (flow, cap, alternatives, legacy-vs-v2 gating). It is dense and long, but not padded — a slightly tighter packaging of the options/profile paragraph would help.

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?

An output schema exists, so return values need no explanation, and the description covers the decision-critical elements: prerequisites, alternatives, resolution limits, and profile behavior. The remaining gap is per-option semantics for the nested options object, which neither schema nor description closes.

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?

With schema description coverage at 19% across 16 params and a 17-key nested options object, the description must carry the load. It explains meaningful semantics for maskSource, baseRoughness/maskRoughness, baseColor, emboss, profile, and roles, but leaves tiling, packing, seamMode, alphaMode/cutoff, normal conventions, displacementMode, and physicalCoverageMeters entirely to the bare schema. Partial compensation, not full.

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 ('turn ONE uploaded image into a full PBR material') and adds a distinguishing constraint ('deterministic, no AI'), which separates it cleanly from sibling material_from_maps and asset_import. An agent knows exactly what this produces 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?

Gives an explicit prerequisite pipeline (upload_create → PUT → upload_complete → material_from_image) and an explicit exclusion with a named alternative: for 4K label/print work use asset_import instead. It also states when legacy mask/emboss args apply (only when profile is omitted). This is textbook when/when-not guidance.

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?