Skip to main content
Glama

ai_modeling_segmentation_preview

Save a colored GLB preview of segment labels while preserving the original model. Use it to inspect segmentation results without altering source geometry or re-exported previews.

Instructions

save a colored GLB preview of segment labels without changing the original 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>"
    },
    "name": "ai_modeling_segmentation_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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?

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, and the description usefully confirms the key behavioral trait that the source model is left untouched while a new file is written. It adds nothing about what state_path must contain, what happens on a mismatched state, or how failures surface, so it goes only slightly past the structured fields.

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 non-destructive guarantee is placed immediately after the action. Brevity is achieved, but it comes at the cost of omitting content rather than by trimming redundancy, which keeps it just under the top mark.

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 with four parameters, a nested object, and no output schema, the description leaves the agent without the rules the schema only partially states (state_path must match the exact source GLB, source_metadata is reused when omitted, preview output must not be re-used as input). It is a one-liner carrying far less than the tool's complexity requires.

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 75%, and the description mentions no parameter at all, so the non-obvious constraints live entirely in the schema. The one gap the schema leaves — destination_path has no description — is also unaddressed, meaning the sentence adds zero meaning beyond the input schema for a 4-parameter tool with a nested source_metadata object.

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?

"save a colored GLB preview of segment labels" gives a specific verb and resource, and the phrase "without changing the original model" separates it from the mutation-oriented siblings such as ai_modeling_segmentation_edit. It stops short of naming any sibling explicitly, so an agent still has to infer the boundary itself.

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 named alternative among ai_modeling_segmentation_edit, ai_modeling_segmentation_inspect, or ai_modeling_segmentation_prompt. The only routing signal is the implied non-destructiveness, which an agent must reconstruct from a negative clause.

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