Skip to main content
Glama

Import 3D model

import_model

Import a 3D model file and render it with rotate, zoom, and scale controls. Without a file path, a default primitive is used.

Instructions

Import a 3D model file (.obj/.fbx/.usd) and render it to a TOP: a File In SOP reading model_path, fed into a Geometry COMP, with a Camera, a Light, and a Render TOP output as a Null. Omit model_path to fall back to a default primitive so the network still builds with no dependencies. Exposes RotateY (spin), Zoom (camera distance) and Scale knobs — the imported-model sibling of create_3d_scene.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoomNoCamera distance from the model along Z (exposed as the Zoom knob).
scaleNoUniform scale applied to the model (1 = imported size).
rotate_yNoInitial rotation of the model around Y in degrees (exposed as the RotateY knob).
model_pathNoPath to a 3D model file (.obj/.fbx/.usd) read by a File In SOP. Omit to fall back to a default primitive so the network still builds and previews with no file dependency.
parent_pathNoParent COMP path the self-contained 'model' container is created inside./project1
expose_controlsNoExpose live RotateY (spin), Zoom (camera distance) and Scale knobs.
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description reveals the exact network structure: File In SOP, Geometry COMP, Camera, Light, Render TOP output as a Null. It also discloses the fallback behavior when model_path is omitted and the exposed knobs. This is rich behavioral context with no contradictions.

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 a single, efficient sentence that front-loads the core action, then details the network, fallback, and sibling relationship. Every clause earns its place with no redundant words.

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

Completeness4/5

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

The description covers the main purpose, network construction, fallback behavior, exposed controls, and the sibling relationship. It does not mention parent_path or container creation, but the schema fully covers those, and there is no output schema to explain. Overall, it is complete for a creation tool with good annotations.

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%, and each parameter already has a detailed description. The tool description adds no new parameter semantics beyond referencing model_path and the knob names, which the schema already documents. Baseline 3 is appropriate.

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

Purpose5/5

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

The description states a specific verb+resource: 'Import a 3D model file (.obj/.fbx/.usd) and render it to a TOP.' It also clearly differentiates from the sibling tool create_3d_scene by calling itself 'the imported-model sibling,' so an agent can tell them apart.

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

Usage Guidelines4/5

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

The description names the alternative create_3d_scene explicitly and distinguishes the use case (importing a model file vs. creating a scene). However, it does not explicitly state 'when not to use' or provide a direct comparison of scenarios, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucasmaher-hash/touch-designer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server