Skip to main content
Glama

sim_control

Controls simulation playback in Omniverse Kit apps by playing, pausing, stopping, or stepping the timeline and returning the resulting simulation state.

Instructions

Play, pause, stop or step the simulation's timeline, and return the state it is left in.

play starts or resumes physics; pause holds it where it is; stop rewinds the timeline, and physics puts bodies back where play found them; step plays for two app updates, then pauses. A robot's first play cooks its collision meshes, and Kit answers nothing until that ends. get_sim_state reads the state without changing it; get_robot_info's joint states and apply_force need it playing or paused.

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": {
      "action": "<action>"
    },
    "name": "sim_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat to do

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the generic non-read-only, non-destructive, non-open-world profile; the description adds substantive behavior the annotations cannot convey — that stop is restorative rather than destructive ('physics puts bodies back where play found them'), that step is bounded to two app updates, and that the first play triggers collision-mesh cooking during which Kit answers nothing. The blocking/latency caveat is a genuinely useful disclosure for an agent sequencing calls.

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?

Front-loaded with the core scope, then per-action semantics, then cross-tool dependencies — a sound order with no filler sentences. It is dense and the per-action clauses run together mid-paragraph, so parsing takes a second pass, but nothing here is redundant.

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?

For a single-enum mutation tool with an output schema already covering return values, the description covers everything an agent needs: action semantics, reversibility of stop, the mesh-cooking block, and which sibling tools depend on the play/pause state. No meaningful gap remains.

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 already 100% and the enum itself is enumerated, but the schema's own parameter text is only 'What to do'. The description supplies the actual meaning of every enum member, including the non-obvious duration semantics of 'step' — meaning that exists nowhere in the structured fields.

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 opening sentence names a specific verb set and resource ('Play, pause, stop or step the simulation's timeline') and states the return contract ('return the state it is left in'). Later sentences explicitly separate this from get_sim_state, get_robot_info, and apply_force, so an agent can route without opening any schema.

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 spells out what each action does and when each applies (play resumes physics, pause holds, stop rewinds, step is two app updates then pause). It also names the read-only alternative ('get_sim_state reads the state without changing it') and states a prerequisite condition ('get_robot_info's joint states and apply_force need it playing or paused'), which is exactly the routing guidance an agent needs.

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