Skip to main content
Glama
whats2000

Isaac Sim MCP Server

by whats2000

create_object

Create primitive objects like cubes and spheres in Isaac Sim with specified position, rotation, scale, color, and physics. Returns the prim path and bounding box for accurate scene placement.

Instructions

Create a primitive object (Cube, Sphere, Cylinder, Cone, Capsule, Plane).

The scale parameter multiplies the primitive's default size. For example, a Cube has default size 2.0, so scale=[0.5, 0.5, 0.5] creates a 1.0m cube.

Returns prim_path, actual_size [x, y, z] in meters, and bounding_box (min/max corners in world coordinates) so you can accurately place other objects relative to this one (e.g. placing a cube on top of a table).

Args: object_type: Type of primitive — Cube, Sphere, Cylinder, Cone, Capsule, or Plane. position: [x, y, z] world position. rotation: [rx, ry, rz] rotation in degrees. scale: [sx, sy, sz] scale factors. color: [r, g, b] color values (0-1). physics_enabled: Enable physics on this object. prim_path: Custom prim path. Auto-generated if not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeNoCube
positionNo
rotationNo
scaleNo
colorNo
physics_enabledNo
prim_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries full burden. It explains the creation behavior, scale effect with example, and return values (prim_path, actual_size, bounding_box). It lacks details on side effects or permissions but is largely transparent.

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 description is well-structured with a clear first sentence and an automated 'Args' section. It is reasonably concise, though the Args list could be shortened by not repeating parameter names already in schema.

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?

Given 7 parameters, no annotations, and an output schema, the description covers creation logic, parameter effects, and return usage. It lacks details on physics behavior or color format but is sufficient for the tool's complexity.

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 0% schema coverage, the description adds significant meaning: lists allowable object types, explains scale with example, notes prim_path auto-generation, and defines return values. Rotation units are specified as degrees, adding value beyond the schema.

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 clearly states the tool creates a primitive object and lists six specific types (Cube, Sphere, etc.), making the purpose distinct from siblings like clone_object or create_robot.

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

Usage Guidelines3/5

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

The description implies when to use (creating primitives) but does not explicitly mention when not to or compare to siblings. It provides practical usage tips (e.g., using return values for placement) but lacks exclusion criteria or alternatives.

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/whats2000/isaacsim-mcp-server'

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