Skip to main content
Glama

Add an object LIVE to the user's open R3 editor

r3_editor_create

The same tool as r3_factory_run (this is its older name): add an object — a cube, sphere, light, physics body … — 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. r3_factory_list lists the factories and their params.

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": {
      "projectId": "<projectId>",
      "factory": "<factory>"
    },
    "name": "r3_editor_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe name of what you make, e.g. "Leg front left" (r3_factory_run's name).
paramsNoFactory options, e.g. {"color": 16711680, "position": {"y": 2}}. Color is a packed RGB integer. Rotations are in RADIANS, not degrees: a quarter turn is Math.PI/2 ≈ 1.5708 (the R3 Inspector shows rotations in degrees: 90°).
factoryYesFactory name, e.g. "Cube", "Sphere", "PhysicsCube". See r3_factory_list.
projectIdYesThe project (r3_project_list).

Output Schema

NameRequiredDescriptionDefault
seqNo
liveYes
rolesYes
savedYes
answerYesThis 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.
editorYes
createdYes
factoryYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / params / description
      Previous value: -"Factory options, e.g. {\"color\": 16711680, \"position\": {\"y\": 2}}. Rotation is in RADIANS, color a packed RGB integer."New value: +"Factory options, e.g. {\"color\": 16711680, \"position\": {\"y\": 2}}. Color is a packed RGB integer. Rotations are in RADIANS, not degrees: a quarter turn is Math.PI/2 ≈ 1.5708 (the R3 Inspector shows rotations in degrees: 90°)."
  2. Changed1 schema field changed
    • addedOutput schema / properties / roles / additionalProperties / properties / readThrough
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "entityRef": {
      +      "type": "string"
      +    },
      +    "property": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "entityRef",
      +    "property"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "The name of what you make, e.g. \"Leg front left\" (r3_factory_run's name).",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • 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"
      +  }
      +]
  5. Changed2 schema fields changed
    • 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",
      -  "factory",
      -  "created",
      -  "roles",
      -  "live",
      -  "saved",
      -  "editor"
      -]New value: +[
      +  "projectId",
      +  "factory",
      +  "created",
      +  "roles",
      +  "live",
      +  "saved",
      +  "editor",
      +  "answer"
      +]
  6. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write, open-world, non-idempotent, non-destructive profile, so the description's job is narrower — and it adds real value by explaining the live-sync semantics: the object is kept in the project's live copy and appears in every R3 tab with the project open immediately. That propagation behavior is not derivable from any annotation. It does not address what happens on repeated calls or name collisions, which matters given idempotentHint=false.

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?

A single dense sentence pair with no filler, and the alias disclosure is front-loaded so an agent does not mistake it for a distinct capability. The em-dash list of object types is slightly loose but earns its place by conveying scope.

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?

An output schema exists, so return values need not be explained, and the description covers the live-propagation behavior plus where to find factory names and options. The remaining gap is sibling disambiguation among the several component/creation tools, which for a crowded namespace is a meaningful but not fatal omission.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents projectId, factory, name, and params with examples and the radians/degrees warning. The description's only param-adjacent contribution is pointing at r3_factory_list for factories and their params, which the schema's factory field already says. Baseline 3 is appropriate.

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 concrete verb and resource ("add an object — a cube, sphere, light, physics body") with examples of what can be created, and explicitly identifies itself as the older name of r3_factory_run, which resolves the duplicate-tool confusion an agent would otherwise hit. It does not distinguish itself from the other creation siblings such as r3_editor_add_component or r3_component_add, so an agent comparing those still has to infer the difference.

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?

Implies usage context by saying "no editor needed and nothing to save," which tells the agent this works without opening the editor, and it routes param discovery to r3_factory_list. There is no explicit when-to-use/when-not statement versus r3_editor_add_component, r3_component_add, or r3_editor_set, so the selection logic among creation tools is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources