Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_uv_mesh

Inspect UV layers, seams, coordinate bounds, island estimates, and topology on a mesh in read-only mode. Choose summary or detailed output to diagnose UV mapping issues.

Instructions

Inspects UV layers, seams, coordinates bounds, island count estimates, and topology on a mesh object. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTarget mesh object name.
task_idNoOptional task or workflow identifier.
uv_layerNoOptional target UV map layer name. Defaults to active UV layer.
detail_levelNoDetail level: 'summary' (bounds, island estimate, seam count) or 'detailed' (includes sample per-face UV coordinates). Defaults to 'summary'.summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the safety profile itself, and 'Read-only' usefully establishes that the tool does not modify the mesh. It also lists the classes of information inspected, but it does not describe side effects such as whether it changes the active UV layer, nor does it explain the return format.

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?

The description is two short sentences and is front-loaded with the core action and inspected properties. 'Read-only' is a compact and important qualifier, and no sentence is wasted.

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 ideally clarify what the inspection returns, especially for the summary versus detailed modes. It adequately states the inspection scope and read-only nature, but return-value detail is left implicit or only partly covered by the input schema.

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 description coverage is 100%, so the input schema already documents name, task_id, uv_layer, and detail_level, including the summary/detailed distinction. The description does not add parameter-specific semantics beyond what the schema already supplies.

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 states a specific verb and resource, 'Inspects ... UV layers ... on a mesh object', and enumerates the inspected properties: seams, coordinate bounds, island count estimates, and topology. It distinguishes itself broadly from UV-editing siblings by saying 'Read-only', but it does not explicitly contrast with neighboring inspection or UV-management tools.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. 'Read-only' signals that it is diagnostic rather than mutating, but it does not tell the agent when to choose this over manage_uv_layers, manage_uv_seams, or other UV inspection/workflow tools.

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