Skip to main content
Glama

ai_modeling_segmentation_inspect

Read-only

Inspect segment labels on a static GLB or pick the nearest face from a ray origin and direction to identify mesh regions for segmentation.

Instructions

inspect segment labels or pick the nearest face of an original static GLB

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_segmentation_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
rayNo
mesh_nameNo
face_indexNo
model_pathYesOriginal static indexed GLB; never use a re-exported preview as the source.
state_pathNoPrevious segmentation state JSON; must match the exact source GLB.
source_metadataNoSource operator children_deleted, children_rename and children_transform_matrix; reused from state when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds only the 'original static GLB' constraint, which the schema's model_path description already states verbatim. It never says what is returned (labels, face id, coordinates) or that state_path must correspond to the same source file.

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

Conciseness3/5

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

A single compact sentence, so it is not bloated, but the two-mode 'or' construction front-loads ambiguity rather than the primary use. The 'pick the nearest face' phrasing also presupposes a ray without saying so.

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?

With six parameters including a nested ray object and a source_metadata object, no output schema, and only 50% schema coverage, the definition is far too thin. An agent would have to guess at mode selection and at the return payload before calling.

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?

Schema coverage is 50% and the description does not compensate. The key mode-selection parameters (ray vs face_index vs mesh_name) and their mutual exclusivity or precedence are left entirely to inference; nothing explains why state_path exists alongside model_path.

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

Purpose3/5

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

The description names two capabilities - inspecting segment labels and resolving the nearest face of an original static GLB - which roughly matches the 'inspect' verb and resource. But it does not clearly differentiate this tool from the sibling segmentation tools (edit, preview, prompt, model_inspect); the 'or' also leaves the primary purpose ambiguous.

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?

No indication of when to use this versus ai_modeling_segmentation_edit, segmentation_preview, or model_inspect. The reader cannot tell whether this is a dry-run, a query-only lookup, or a precondition step.

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