Skip to main content
Glama

ai_modeling_uv_inspect

Read-only

Inspect existing UV islands and utilization in a GLB, optionally selecting geometry by UV coordinates or a 3D ray for targeted review.

Instructions

inspect existing UV islands and utilization, optionally pick by UV coordinates or a 3D ray

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

Input Schema

NameRequiredDescriptionDefault
rayNoNearest 3D surface pick in GLB world coordinates, at the stored pose.
pickNo
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that only pre-existing UVs are inspected ('existing'), but does not disclose what is returned, whether pick and ray can be combined, or which takes precedence — meaningful for openWorldHint=true on what is otherwise a local GLB read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loading the core action and folding the optional modes into a trailing clause. Nothing is wasted or repeated from the schema.

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?

There is no output schema, so the description should carry the return contract; it names 'islands and utilization' but not the shape of picked results. For a 4-parameter tool with nested objects, the definition is minimally adequate but leaves how the two selection modes combine unexplained.

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?

With 75% schema description coverage, the baseline is 3. The description does add meaning for the undocumented 'pick' object by framing it as coordinate-based selection, but it does not clarify how 'pick' and 'ray' interact or that they are alternate modes.

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?

The description gives a specific verb and resource: 'inspect existing UV islands and utilization'. The word 'existing' distinguishes it from the generate/apply family (ai_modeling_uv_generate, ai_modeling_uv_apply) by signalling a read of already-authored UVs, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

It outlines the two optional selection modes ('pick by UV coordinates or a 3D ray'), which is implied usage context, but gives no guidance on when to choose this over uv_context, uv_preview, or model_inspect, and no prerequisites or exclusions.

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