Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

simulation_start

Start or queue an Isaac Sim experimental job, optionally pinning inline or server-side JSON/YAML cases; reuse request_id to return identical jobs or set a new ID for distinct runs.

Instructions

Start or queue an experimental Isaac job, optionally pinning an inline case or server-side JSON/YAML case. Reusing the same request_id with identical parameters returns the original job; use a new ID for a distinct run. continue_on_controller_error keeps physics running after a controller failure. archive_verified_objects requires a pinned stream case.

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": {
      "scene_id": "<scene_id>"
    },
    "name": "simulation_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseNo
seedNo
stepsNo
scene_idYes
case_pathNo
request_idNo
archive_verified_objectsNo
continue_on_controller_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It usefully explains queueing, request_id idempotency, and the effects of continue_on_controller_error and archive_verified_objects, but omits whether execution is asynchronous, what is returned, and broader job lifecycle or permission behavior.

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 front-loaded and efficiently sized at four sentences. It avoids filler, though some parameter details are packed tersely without a clear structural breakdown.

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

Completeness2/5

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

For an eight-parameter start/queue tool with no annotations, no output schema, and no schema descriptions, the definition leaves important gaps. It does not explain scene_id, seed, or steps, nor does it describe what starting a job returns or how the resulting job is tracked.

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

Parameters2/5

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

Schema description coverage is 0% across eight parameters, so the description must compensate. It explains case/case_path, request_id, and two boolean flags, but leaves the required scene_id plus seed and steps undocumented, which is a major gap.

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?

States a specific verb and resource: start or queue an experimental Isaac job, with optional case pinning. It does not explicitly differentiate from siblings such as simulation_pause, simulation_resume, or job_status, so it falls short of a 5.

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?

Provides useful usage semantics such as request_id idempotency and the requirement for archive_verified_objects. However, it gives no explicit when-to-use guidance relative to alternatives like job_status, simulation_pause, or simulation_resume.

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