Skip to main content
Glama

ai_modeling_uv_preview

Save a separate GLB preview highlighting one UV island on a 3D model to inspect UV layout and mesh mapping without performing any unwrap.

Instructions

save a separate GLB preview highlighting one UV island on the 3D model

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": {
      "model_path": "<model_path>",
      "destination_path": "<destination_path>",
      "island_id": "<island_id>"
    },
    "name": "ai_modeling_uv_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
island_idYes
mesh_namesNoExact visible mesh node names; omit to inspect all meshes in the default scene.
model_pathYesSelf-contained GLB with existing UV coordinates; no unwrap is performed.
destination_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the mutation/safety profile is already covered. The description usefully implies the source model is untouched because the preview is 'separate', but it says nothing about overwriting an existing destination file, required permissions, or what is returned after the write.

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?

A single front-loaded sentence with no filler; the action and key constraint ('one UV island', 'separate') come first. It is efficient, though its brevity borders on under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool that produces a file with no output schema, the definition leaves important gaps: return value, overwrite semantics, and how island_id is obtained. The schema's note about self-contained GLB and no unwrap is the only deeper context, and that lives in the schema, not the description.

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

Parameters2/5

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

With only 50% schema description coverage, the description must compensate but largely does not. It clarifies that island_id refers to a single UV island, yet gives no hint where island IDs come from (e.g., an inspect step) and adds nothing about destination_path format or overwrite behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and artifact: 'save a separate GLB preview highlighting one UV island on the 3D model'. The word 'separate' plus 'GLB preview' distinguishes it from in-canvas preview/share siblings, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. An agent cannot tell from the description whether this is the right tool for confirming island IDs versus ai_modeling_uv_inspect or ai_modeling_segmentation_preview; only the phrase 'preview highlighting one UV island' implies intent.

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

Deploy Server

Other Tools