Skip to main content
Glama
whats2000

Isaac Sim MCP Server

by whats2000

create_action_graph

Create and wire an OmniGraph Action Graph programmatically to control simulation behavior using nodes, connections, and attribute values.

Instructions

Create and wire an OmniGraph Action Graph.

Builds a complete Action Graph with nodes, connections and attribute values using og.Controller.edit(). This is the programmatic equivalent of creating an Action Graph in the visual editor.

Args: graph_path: USD prim path for the graph (default "/World/ActionGraph"). nodes: List of node definitions. Each dict has: - "path": Node path relative to graph (e.g. "OnPlaybackTick") - "type": OmniGraph node type (e.g. "omni.graph.action.OnPlaybackTick") connections: List of [source_attr, target_attr] pairs for wiring nodes. Each attr is "NodePath.outputs:attrName" or "NodePath.inputs:attrName". values: List of attribute value overrides. Each dict has: - "attr": Full attribute path (e.g. "ScriptNode.inputs:script") - "value": The value to set evaluator: Graph evaluator type (default "push"). script_file: Convenience shortcut — path to a local Python script file. When provided, automatically creates OnPlaybackTick → ScriptNode nodes, wires them, and attaches the script file (sets usePath + scriptPath). The nodes and connections parameters are ignored when script_file is set.

Example (inline script): create_action_graph( values=[ {"attr": "ScriptNode.inputs:script", "value": "def compute(db): ..."} ] )

Example (script file — one-step): create_action_graph( script_file="/path/to/controller.py" )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
graph_pathNo/World/ActionGraph
nodesNo
connectionsNo
valuesNo
evaluatorNopush
script_fileNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Discloses use of og.Controller.edit() and the script_file shortcut that overrides nodes/connections. However, it does not mention side effects like overwriting existing graphs, error handling, or permission requirements. With no annotations, this is moderate but incomplete.

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?

Well-organized with Args and Example sections. Each sentence adds value, though some repetition exists (e.g., 'programmatic equivalent of creating an Action Graph in the visual editor' could be merged). Nevertheless, it is efficient and front-loaded.

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 6 parameters, no required ones, and the presence of an output schema (reducing burden on description), the description covers all parameters with examples and behavioral notes. Missing details on return value or error cases, but acceptable for the complexity level.

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?

Despite 0% schema description coverage, the description thoroughly explains all 6 parameters with structure, defaults (graph_path default '/World/ActionGraph', evaluator default 'push'), and examples. The script_file parameter is clarified as a convenience shortcut with behavioral implications.

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?

Clearly states 'Create and wire an OmniGraph Action Graph' and differentiates from sibling 'edit_action_graph' by explicitly describing creation. Provides specific details on building nodes, connections, and attribute values, making the purpose unambiguous.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like 'edit_action_graph'. Examples imply usage scenarios but do not state prerequisites, exclusions, or when not to use. The description assumes the agent knows when graph creation is needed.

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