Skip to main content
Glama

ai_modeling_uv_layout

Exports a model's current UV layout as a local 1024px PNG, matching the browser UV Download output, with optional mesh selection and island highlighting.

Instructions

export the current UV layout as a 1024px PNG locally, matching the browser UV Download function

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

Input Schema

NameRequiredDescriptionDefault
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
highlight_islandNoOptional viewer highlight; omit for the webpage Download output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write nature is covered. The description adds useful context (fixed 1024px resolution, local write, parity with the browser function) but says nothing about overwrite behavior, whether the destination must exist, or required auth/permissions.

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 that names the output artifact and resolution first, with no filler. The trailing 'matching the browser UV Download function' phrase earns its place by pinning down expected output semantics.

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

Completeness3/5

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

For a tool that writes a file there is no output schema and no statement of what is returned (path, confirmation, or error modes), and destination_path semantics are left implicit. The description is adequate to attempt a call but not complete for a file-writing operation.

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?

Schema coverage is 75%, with mesh_names, model_path and highlight_island documented in the schema itself. The one undocumented parameter, destination_path, is only obliquely covered by 'locally' in the description, so meaning added beyond the schema is minimal but the baseline is met.

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 specific verb and resource (export the current UV layout) plus the concrete output (1024px PNG written locally), and anchors it to the browser UV Download function. It is clear what the tool produces, though it does not name a sibling like uv_preview or uv_inspect to sharpen the distinction.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only routing hint is indirect: omitting highlight_island reproduces webpage Download output, which hints at usage but never states it as a rule.

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