Skip to main content
Glama

Make a tileable texture set (colour, normal, roughness) from a recipe

r3_texture_create
Destructive

Make a matching, seamlessly tiling texture SET for a material: a colour map, a normal map and a packed ambient-occlusion / roughness / metalness map, rendered by R3 from a procedural recipe (seeded noise, stones, bricks …). Nothing is uploaded and it is free. The maps are stored as images in the account (the owner sees them in the Images browser as " · albedo.png" …).

Start from a preset (gravel, sand, concrete, bricks, brushedMetal) with optional controls: seed (another variation), scale (an integer: finer pattern), colours (the ramp's "#rrggbb" stops, exactly as many colours as the preset has: gravel 3, sand 2, concrete 3, bricks 3, brushedMetal 3), contrast, bumpiness (normal strength), roughness {min, max} (from the smooth parts to the rough parts), metalness (0 = not metal, 1 = metal; metal looks dark without an environment map in the scene), size (256 / 512 / 1024 / 2048, default 1024), tileWorldSize (metres one tile covers, default 1), height (also store a 16-bit height map). Or pass a full recipe (r3_docs_read("TEXTURE_RECIPES.md") has the format and every preset's recipe). An invalid recipe is refused with the path of the problem.

Pass apply {projectId, material, repeat | worldSize (a number, or {x, y} for a long strip)} to put it on a material in the same call (as r3_texture_apply). You cannot see the texture: the answer gives numbers (mean colour, brightness range, height spread, seam check) and the colour map's url; r3_editor_capture shows it in an open editor. Names are unique per account. Each call makes a NEW set; reuse a set with r3_texture_apply.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWhat the owner sees, e.g. "Gravel path". Unique in the account.
sizeNo256, 512, 1024 (default) or 2048 pixels square.
applyNoAlso wire it to a material: {projectId, material, repeat | worldSize}.
presetNoA preset: gravel, sand, concrete, bricks, brushedMetal.
recipeNoOr a full recipe (format "r3-texture-recipe", version 1).
controlsNoWith a preset: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, metalness, size, tileWorldSize, height}. colours: exactly the preset's number of "#rrggbb" stops (gravel 3, sand 2, concrete 3, bricks 3, brushedMetal 3).

Output Schema

NameRequiredDescriptionDefault
mapsYes
nameYes
sizeYes
setIdYes
statsYes
answerYesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
appliedYes
warningsYes
tileWorldSizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / maps / additionalProperties / properties / pixelHash
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / controls / description
      Previous value: -"With a preset: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, size, tileWorldSize, height}. colours: exactly the preset's number of \"#rrggbb\" stops (gravel 3, sand 2, concrete 3, bricks 3)."New value: +"With a preset: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, metalness, size, tileWorldSize, height}. colours: exactly the preset's number of \"#rrggbb\" stops (gravel 3, sand 2, concrete 3, bricks 3, brushedMetal 3)."
    • changedInput schema / properties / preset / description
      Previous value: -"A preset: gravel, sand, concrete, bricks."New value: +"A preset: gravel, sand, concrete, bricks, brushedMetal."
  3. Changed4 schema fields changed
    • changedInput schema / properties / apply / properties / repeat / description
      Previous value: -"How often the texture repeats across the surface (the same on every map). Default 1."New value: +"How often the texture repeats across the surface, on both axes and every map."
    • addedInput schema / properties / apply / properties / worldSize / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "properties": {
      +      "x": {
      +        "type": "number"
      +      },
      +      "y": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "x",
      +      "y"
      +    ],
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / apply / properties / worldSize / description
      Previous value: -"Or: the surface size in metres; repeat = worldSize / the set's tile size (1 m for the presets), e.g. 1000 for a 1 km terrain."New value: +"Or: the surface size in metres, a number (square) or {x, y} (its two sides, e.g. {\"x\": 2, \"y\": 40} for a 2 m × 40 m path); repeatX = x / the set's tile size (1 m for the presets), repeatY = y / it. Neither given: the mesh(es) using the material are measured."
    • removedInput schema / properties / apply / properties / worldSize / type
      Removed value: -"number"
  4. Changed1 schema field changed
    • changedInput schema / properties / controls / description
      Previous value: -"With a preset: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, size, tileWorldSize, height}."New value: +"With a preset: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, size, tileWorldSize, height}. colours: exactly the preset's number of \"#rrggbb\" stops (gravel 3, sand 2, concrete 3, bricks 3)."
  5. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (destructive/non-idempotent/openWorld), the description adds real context: nothing is uploaded, it is free, maps land as named images visible in the Images browser, names are unique per account, an invalid recipe is rejected with the problem's path, and each call creates a fresh set. It does not cover permissions/quotas, which is the main remaining gap; the 'creates a NEW set' note is consistent with the non-idempotent annotation.

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?

It is front-loaded with the core purpose and the destructive/new-set caveat lands early; every paragraph carries usable information. It is on the long side and the controls enumeration duplicates schema text, costing a point.

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?

For a 6-parameter tool with nested objects and an output schema, the description covers the creation model, presets vs recipes, the optional apply step, naming uniqueness, and how to visually verify. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the metalness caveat ('metal looks dark without an environment map'), the per-preset colour-stop counts, and the TEXTURE_RECIPES.md pointer for the free-form `recipe`/`controls` objects. That nudges it above baseline, though much of the controls list restates 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?

The opening sentence names a specific verb and concrete output set (colour, normal, packed AO/roughness/metalness) and the source (a procedural recipe / preset). It also distinguishes itself from r3_texture_apply and r3_texture_update by stating 'Each call makes a NEW set; reuse a set with r3_texture_apply.' An agent can tell exactly what this produces versus its siblings.

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?

It gives two explicit entry paths (preset with optional controls, or a full `recipe`) and names the doc for the recipe format. It states the alternative for reuse (r3_texture_apply) and the inspection route (r3_editor_capture) for seeing the result. When-to-use and when-not-to-use are both covered.

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