Skip to main content
Glama

texture_mesh

Textures existing 3D meshes from a text prompt, creating PBR maps, UV layouts, and GLB/FBX outputs so untextured models become render-ready.

Instructions

Texture an existing mesh (GLB, glTF, OBJ, STL, PLY or FBX; untextured is fine) from a text prompt.

Builds everything a PBR material needs: a fresh UV layout (keep_uvs=True keeps the mesh's own), a base color painted by FLUX.2 Klein on views clay renders around the mesh and projected into the UVs (style_image: an optional picture whose colours and style the front view follows), ambient occlusion, a normal map from a bump derived from the painted detail (bump 0 to 1, 0 for none), and roughness (base value, rougher where the paint is darker) and metallic values. denoise (0.6 to 1.0) is how freely views are painted: lower keeps more of the clay shading. Best on clean meshes of a few thousand to 50k faces, for example from retopologize_mesh. Outputs a GLB and an FBX with embedded textures, plus the painted views as PNGs. About 1 to 2 minutes on the GPU, then a few seconds in Blender on the CPU.

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": {
      "input_mesh": "<input_mesh>",
      "prompt": "<prompt>"
    },
    "name": "texture_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
bumpNo
seedNo
viewsNo
promptYes
denoiseNo
keep_uvsNo
metallicNo
roughnessNo
input_meshYes
output_dirNo
style_imageNo
texture_sizeNo
idle_timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it enumerates the produced PBR channels (UV layout, base color, AO, normal from bump, roughness, metallic), the model used, GPU/CPU timing, and the concrete artifacts emitted (GLB, FBX with embedded textures, PNG views). It does not cover overwrite behavior for output_dir, error handling on bad meshes, or resource/permission requirements.

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-loaded with the core action in one sentence, then pipeline detail, then applicability, then outputs and timing — a logical order with no filler. The nested parentheticals in the middle paragraph are dense and slightly hard to scan in one pass, costing a point.

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?

For a 13-parameter generative tool with no annotations and no output schema, the description supplies the pipeline, the returned artifacts, and rough runtime, which is most of what an agent needs. The missing pieces are the four undocumented parameters (seed, texture_size, output_dir, idle_timeout_seconds) and any failure-mode guidance.

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 0%, so the description must compensate for all 13 parameters and it explains the non-obvious ones with real semantics: keep_uvs, bump (0–1, 0 for none), denoise (0.6–1.0 with the meaning of lower values), style_image, views, roughness/metallic behavior, and input_mesh formats. seed, texture_size, output_dir, and idle_timeout_seconds are left completely unexplained, which keeps it below a 5.

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 ('Texture an existing mesh') plus the accepted input formats, and the phrase 'existing mesh' implicitly separates it from mesh-generation siblings like generate_mesh. An agent can tell immediately that this consumes a mesh rather than producing one.

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?

Gives real usage context: 'untextured is fine', 'Best on clean meshes of a few thousand to 50k faces, for example from retopologize_mesh', which routes the agent to a preprocessing sibling for heavy meshes. It lacks explicit when-not-to-use conditions or naming of a contrasting alternative, so it stops short of a 5.

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