Skip to main content
Glama

Import 3D model

import_model

Import and render a 3D model (.obj, .fbx, .usd) with camera, light, and controls for rotation, zoom, scale. Defaults to a primitive if no file is provided.

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
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.
rotate_yNoInitial rotation of the model around Y in degrees (exposed as the RotateY knob).
zoomNoCamera distance from the model along Z (exposed as the Zoom knob).
scaleNoUniform scale applied to the model (1 = imported size).
expose_controlsNoExpose live RotateY (spin), Zoom (camera distance) and Scale knobs.
parent_pathNoParent COMP path the self-contained 'model' container is created inside./project1
Behavior5/5

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

Annotations indicate mutation and non-destructive behavior; the description elaborates on the exact network built (File In SOP, Geometry COMP, Camera, Light, Render TOP), fallback logic, and exposed controls. No contradiction between description and annotations.

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?

Two sentences convey file types, network structure, fallback, controls, and sibling relationship. Every part is essential; no redundancy.

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?

Covers inputs, fallback, controls, and network components. Lacks mention of error handling or file accessibility, but for a 6-param tool with no required parameters and no output schema, it is adequately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds value by linking parameters (RotateY, Zoom, Scale) to user-facing knobs, clarifying their role in the control interface beyond the schema's literal definition.

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 specifies 'Import a 3D model file (.obj/.fbx/.usd) and render it to a TOP' with detailed network components, and explicitly distinguishes from sibling 'create_3d_scene' by calling itself 'the imported-model sibling'.

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?

Provides clear context on when to omit model_path (fallback to default) and hints at usage via sibling reference. However, it lacks explicit when-not-to-use or alternative selection criteria beyond the sibling mention.

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/Pantani/tdmcp'

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