Skip to main content
Glama

Change a texture set: make a new version of it

r3_texture_update

Change a texture set the account owns: its look (controls: seed, scale, colours, contrast, bumpiness, roughness {min, max}, metalness, size, tileWorldSize, height, applied to the set's own recipe; scale multiplies its pattern, so 2 is twice as fine as now) or a whole new recipe (read the current one with r3_texture_read, change it, pass it here). The set itself never changes: the change is saved as a new version under the same name (the user's lists show the latest), with new maps, and every project and release that uses an older version's maps keeps them. Give name only to make a separate copy under that name instead. The same recipe as the latest version saves nothing. The answer names the user's projects still on an older version; put the new set on a material with r3_texture_apply when the user wants it. An invalid change is refused with the path of the problem. Counts as one render toward your hourly texture budget.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOnly to make a separate COPY under this name. Default: a new version of the same set, same name.
setIdYesThe set to change (r3_texture_create / r3_texture_read answer it). The account's own.
recipeNoOr a whole new recipe (format "r3-texture-recipe", version 1).
controlsNoChanges to its recipe: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, metalness, size, tileWorldSize, height}.

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.
versionYes
warningsYes
unchangedYes
previousIdYes
previousInUseYes
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. Changed4 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The new set's name. Default: the old name with the next number (\"Gravel 2\")."New value: +"Only to make a separate COPY under this name. Default: a new version of the same set, same name."
    • addedOutput schema / properties / unchanged
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / version
      Added value: +{
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "setId",
      -  "previousId",
      -  "name",
      -  "size",
      -  "tileWorldSize",
      -  "maps",
      -  "stats",
      -  "warnings",
      -  "previousInUse",
      -  "answer"
      -]New value: +[
      +  "setId",
      +  "previousId",
      +  "name",
      +  "size",
      +  "tileWorldSize",
      +  "maps",
      +  "stats",
      +  "warnings",
      +  "version",
      +  "unchanged",
      +  "previousInUse",
      +  "answer"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / controls / description
      Previous value: -"Changes to its recipe: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, size, tileWorldSize, height}."New value: +"Changes to its recipe: {seed, scale, colours, contrast, bumpiness, roughness: {min, max}, metalness, size, tileWorldSize, height}."
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial context beyond annotations: non-destructive versioning with old maps preserved, no-op when the recipe matches the latest version, invalid input refused with the problematic path, and a render-charge cost against the hourly texture budget. These are exactly the operational facts an agent needs and annotations do not convey.

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?

Dense but front-loaded: the core versioning contract comes first, followed by copy semantics, no-op behavior, and budget cost. The single long paragraph with parenthetical asides is slightly heavy to parse, but virtually every sentence carries actionable information.

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 nested-object mutation with an output schema, the description covers versioning effects, copy mode, no-op detection, error behavior, downstream project references, and cost. Nothing an agent needs to invoke correctly is missing, and return-value detail is reasonably left to the output schema.

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 coverage is 100%, so the structured fields already define the parameters, but the description adds genuine semantics: `scale` multiplies the pattern (2 = twice as fine), enumerates the control fields, and clarifies that `name` means 'make a copy' rather than rename. That extra meaning lifts it above the baseline 3.

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 (change/update) and resource (texture set) and precisely describes the versioning semantics: the change is saved as a new version under the same name while existing projects keep older maps. This distinguishes it clearly from siblings like r3_texture_create and r3_texture_apply.

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?

Explicitly routes between the two modes (controls vs whole recipe), explains how to obtain the recipe via r3_texture_read, states that `name` switches to copy semantics, and points to r3_texture_apply for putting the new set on a material. Exclusions and alternatives are all named.

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