omniverse-mcp

Overview Schema Source Related Servers Discussions Admin

create_robot

Adds a robot to an Isaac Sim stage by built-in name (e.g., Franka, Spot, G1) or USD file path, with optional position, rotation, and prim path.

Instructions

Add a robot: one of Isaac Sim's asset library by name, or a robot's own USD file.

    Available: franka, ur10, carter, jetbot, g1, go1, go2, h1, spot, anymal. Or a USD file as robot_type: 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 file.

Input Schema

Name	Required	Description
`position`	No	[x, y, z] in the stage's units (usually metres)
`rotation`	No	Euler angles [rx, ry, rz] in degrees, or a quaternion [w, x, y, z]
`prim_path`	No	Where to put it; made up from the name when empty
`robot_type`	Yes	A robot's name (franka, g1, spot, ...) or a USD file's path

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Oct 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-vs-read nature is already conveyed. The description adds the prim-naming default when prim_path is empty, which is useful, but omits whether an existing prim is overwritten or whether a stage must be loaded first.

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?

The definition is short and front-loaded, with the resource type and alternatives stated first. The opening phrasing ('one of Isaac Sim's asset library by name') is slightly awkward, costing it a point on polish.

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?

With an output schema present and 100% parameter coverage, the description needn't explain returns. It covers names, path formats, and naming defaults well; the only gap is scene-precondition and overwrite behavior for a mutation tool.

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?

Schema coverage is 100% and the schema has no enum for robot_type, so the description's enumeration of valid robot names (franka, ur10, carter...) plus the USD path formats (Kit machine path, URL, /Isaac/... path) is real added meaning. The prim_path naming default also clarifies behavior beyond the schema.

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?

The description opens with a specific verb and resource: 'Add a robot' distinguished as either an asset-library name or a robot's own USD file. This clearly separates it from the generic create_prim sibling, though it does not explicitly contrast with create_prim by name.

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 tells the agent the two calling modes (library name vs. USD path) and enumerates the available names, giving clear context for selection. It does not state when to prefer create_prim over this tool, so an explicit exclusion is missing.

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