R3

Add ANY component LIVE to the user's open R3 editor

r3_editor_add_component

The same tool as r3_component_add (this is its older name): add one component of ANY registered type — a collider, a rigid body, a joint, a light, a material, a geometry … — with its values and references set before it is created, kept at once in the project's live copy: every R3 tab with the project open shows it now, no editor needed and nothing to save. Use r3_editor_create for a ready-made object.

type is the short type name, e.g. "ColliderCuboid" (an unknown type is refused with the list). values take r3_component_set's shapes: a plain value {"friction": 0.2}; a value component as the keys to set {"halfExtents": {"x": 2, "y": 0.5, "z": 1}}; a reference as the target's entityRef or id {"rigidBody": "rigidbody_dynamic_1"} — a component of THIS project, of a type the slot accepts. Example — swap a rigid body's collider: add a ColliderCuboid with {"rigidBody": …, "halfExtents": …}, then r3_editor_delete the old collider (mode "one").

Input Schema

Name	Required	Description
`type`	Yes	The component type, e.g. "ColliderCuboid", "RigidBodyFixed", "LightPoint".
`values`	No	Its values, e.g. {"rigidBody": "rigidbody_dynamic_1", "halfExtents": {"x": 2}, "friction": 0.2}.
`projectId`	Yes	The project (r3_project_list).

Output Schema

Name	Required	Description
`seq`	No
`live`	Yes
`type`	Yes
`saved`	Yes
`answer`	Yes	This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
`editor`	Yes
`created`	Yes
`entityRef`	Yes
`projectId`	Yes
`componentId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedOutput schema / properties / editor / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "lastActiveAgoMs": {
-        "type": "number"
-      },
-      "lastActiveAt": {
-        "type": "string"
-      },
-      "openProjects": {
-        "anyOf": [
-          {
-            "items": {
-              "additionalProperties": false,
-              "properties": {
-                "id": {
-                  "type": "string"
-                },
-                "name": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                }
-              },
-              "required": [
-                "id",
-                "name"
-              ],
-              "type": "object"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "openedAt": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "openedAt",
-      "lastActiveAt",
-      "lastActiveAgoMs",
-      "openProjects"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "frames": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "advancing": {
+                "type": "boolean"
+              },
+              "frameSeen": {
+                "type": "boolean"
+              },
+              "sceneShown": {
+                "type": "boolean"
+              },
+              "visible": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "advancing",
+              "visible",
+              "sceneShown",
+              "frameSeen"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "lastActiveAgoMs": {
+        "type": "number"
+      },
+      "lastActiveAt": {
+        "type": "string"
+      },
+      "openProjects": {
+        "anyOf": [
+          {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "id",
+                "name"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "openedAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "openedAt",
+      "lastActiveAt",
+      "lastActiveAgoMs",
+      "openProjects"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedOct 15, 2026

addedOutput schema / properties / answer

Added value: +{
+  "description": "This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "projectId",
-  "type",
-  "componentId",
-  "entityRef",
-  "created",
-  "live",
-  "saved",
-  "editor"
-]New value: +[
+  "projectId",
+  "type",
+  "componentId",
+  "entityRef",
+  "created",
+  "live",
+  "saved",
+  "editor",
+  "answer"
+]

First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only provide safety hints; the description adds the crucial live-sync semantics: the component is kept at once in the project's live copy, every open R3 tab shows it immediately, and nothing needs saving. It also discloses the failure mode for unknown types (refused with the list) and that references must resolve to a component in THIS project of an accepted type.

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 alias identity and live behavior, then parameters, then an example. Slightly dense with backtick-heavy inline detail, but every sentence carries actionable information.

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?

With an output schema present, return values need not be described. The description covers alias identity, live propagation behavior, type/value/reference syntax, refusal behavior, and the follow-up sibling call — complete for a 3-param mutation tool.

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 100% (baseline 3), but the description genuinely adds meaning: `type` is the short type name with examples, and `values` accepts three distinct shapes — plain values, value components given as keys to set, and references as entityRef or id. That is detail the schema's free-form object cannot convey.

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?

States a specific verb (add) and resource (one component of ANY registered type) and explicitly identifies the alias relationship to r3_component_add. It distinguishes itself from siblings r3_editor_create (ready-made object) and r3_component_set (values shapes), so an agent can route correctly.

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?

Names the alternative (r3_editor_create) and the condition that selects it, and gives an end-to-end example workflow (add ColliderCuboid with rigidBody/halfExtents references, then r3_editor_delete in mode "one"). Explicit when-to-use plus a concrete chained scenario.

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

All R3 tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?