Skip to main content
Glama

create_robot

Add a robot to an Isaac Sim stage by asset name or USD file path, placing it at a chosen prim path and adjusting units and orientation to match the stage.

Instructions

Add a robot to the stage as a reference: one of Isaac Sim's asset library by name, or a robot's USD file.

Names, which need Isaac Sim: franka, ur10, carter, jetbot, g1, go1, go2, h1, spot, anymal. A USD file as robot_type is a path on the Kit app's machine, a URL, or a path in Isaac Sim's asset library (/Isaac/...). Without prim_path, the prim is named after the robot or the file: /World/Franka, or /World/MyBot for MyBot.usd. A prim already at prim_path, or a file that can't be opened, is an error. A file whose upAxis isn't the stage's is stood upright on it, as Kit stands a dropped file, and the answer says so: Isaac Sim's robots are Z-up, so each is turned on a Y-up stage. A file that authors no upAxis is left as it is. A file whose metersPerUnit or kilogramsPerUnit isn't the stage's is brought to the stage's units, as Kit's metrics assembler brings a dropped file with its physics rules: scaled, its physics values converted, and the answer says so; one that authors neither is left as it is. position and rotation stay in the stage's frame. For anything but a robot, use create_prim; get_robot_info then lists the robot's joints.

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": {
      "robot_type": "<robot_type>"
    },
    "name": "create_robot"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionNo[x, y, z] relative to the parent prim, in the stage's units (get_sim_state's meters_per_unit)
rotationNoEuler angles [rx, ry, rz] in degrees, or a quaternion [w, x, y, z]
prim_pathNoWhere to put it; made up from the name when empty
robot_typeYesA robot's name (franka, g1, spot, ...) or a USD file's path

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • changedInput schema / properties / position / description
      Previous value: -"[x, y, z] in the stage's units (usually metres)"New value: +"[x, y, z] relative to the parent prim, in the stage's units (get_sim_state's meters_per_unit)"
  2. First observedv0.2.2

TDQS

A4.8/5.0
Behavior5/5

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

The annotations only say the tool is non-read-only and non-destructive. The description adds a lot beyond that: the default prim naming rule, the error cases (prim already exists, file can't be opened), and up-axis correction that is reported in the answer. It also covers unit and physics conversion matching Kit's metrics assembler, and notes that position and rotation stay in the stage frame.

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?

It is front-loaded with the purpose, but the middle is a dense run-on paragraph about up-axis and unit handling. The phrasing is awkward in places ("stood upright on it", "the answer says so"). That content is useful but could be tighter or structured as a list.

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?

An output schema exists, so return values need no explanation. Inputs, defaults, error conditions, side effects and related tools are all covered, which makes the description complete for this moderately complex mutation tool.

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?

Schema coverage is 100%, yet the description still adds real meaning. It gives the full list of valid robot names, which the schema lacks as an enum, and the accepted path forms: local path, URL, or /Isaac/ library path. It also explains how the default prim_path is derived, e.g. /World/Franka or /World/MyBot.

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?

It states a specific verb and resource: add a robot to the stage as a USD reference, either from Isaac Sim's asset library by name or from a USD file. It also separates itself from create_prim, which is for anything but a robot.

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

Usage Guidelines5/5

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

It gives the alternative explicitly ("For anything but a robot, use create_prim") and names the follow-up tool, get_robot_info, for listing joints. It also states a prerequisite: library names need Isaac Sim.

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