Isaac Sim MCP Server

by whats2000

Overview Schema Source Related Servers Discussions Admin

load_environment

Load a pre-built environment into the Isaac Sim scene by name or search term, with automatic rotation and scaling corrections. Get the prim_path and floor_height for precise placement.

Instructions

Load a pre-built environment into the scene. Supports fuzzy matching. Call list_environments first to see available options.

Many shipped environments are authored Y-up and/or in centimeters; those are rotated and rescaled to match the stage, and the response reports what was applied under "corrections". Read prim_path from the response rather than assuming it — it defaults to a named child of /Environment.

"bounds" carries two different heights, so use the right one: floor_height — the surface objects rest on, measured from the environment's collision floor. Place with position=[x, y, floor_height]. bounds_min_z — the lowest authored geometry (trim, a recessed drain, a sunk prop). Not a placement height. floor_height_source says which was used. When it reads "bounds_min_z" no collision floor could be measured and floor_height is a fallback that may be below the real surface — floor_height_warning explains it.

Args: environment: Environment name or search term (e.g. "warehouse", "hospital", "office"). prim_path: Prim path for the loaded environment. Defaults to /Environment/, which keeps it separate from the stage's default lighting and lets clear_scene remove it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`prim_path`	No
`environment`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.1Sep 22, 2026
- addedInput schema / properties / prim_path / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / prim_path / default
```
Previous value: -"/Environment"New value: +null
```
- removedInput schema / properties / prim_path / type
```
Removed value: -"string"
```
First observedv0.1.0Jun 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden, and it does so thoroughly. It discloses fuzzy matching, automatic Y-up/centimeter corrections, response fields like 'corrections' and 'floor_height_source', fallback behavior, and how prim_path affects scene organization and clear_scene removal.

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 long but every sentence adds actionable information. It is front-loaded with the purpose and prerequisite, then logically organizes caveats about corrections and floor height so an agent can place objects correctly without re-reading the output schema.

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

Completeness5/5

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

Given two parameters, no annotations, and a complex output, the description covers prerequisites, naming, fuzzy matching, coordinate-system corrections, placement semantics, and response interpretation. An agent has everything needed to invoke the tool and interpret the result correctly.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description fully compensates. It defines environment as a name or fuzzy search term with examples, and prim_path with its default, behavioral implications, and relationship to clear_scene.

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 opens with a specific verb and resource: 'Load a pre-built environment into the scene.' It clarifies this is distinct from arbitrary USD loading by calling it 'pre-built' and directing users to list_environments, effectively differentiating it from siblings like load_usd.

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?

It explicitly says to call list_environments first, providing a clear prerequisite and workflow. It also explains when prim_path defaults are desirable, but it does not explicitly discuss when to choose an alternative such as load_usd or when not to use this tool.

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