Skip to main content
Glama

Read live component values from the user's open R3 editor

r3_editor_inspect
Read-only

Read what components hold RIGHT NOW in an R3 tab that has the project open: runtime values included — a moving body's position while the project runs. Use it to debug live behaviour. It needs a tab with the project open (r3_editor_open opens one). r3_component_read reads the kept values without a tab.

Select with any of: ids (component ids from r3_project_load), type ("Mesh", "RigidBodyDynamic", …) and entityRef; they combine. fields keeps only the properties you name (e.g. ["position", "rotation"]). At most 50 components per call; a larger answer is refused with how to narrow it.

Values are in r3_component_read's shape (value components inline, references as entityRefs), so they can be handed to r3_component_set. The project must be open in the editor (r3_editor_open opens it). Read-only: nothing is changed.

Script problems: scriptDiagnostics lists the recent errors and warnings of the Code components read (compile / start / runtime errors, warnings such as AmbiguousEntityRefError), each with its name, message, count and last time, since the last Run. Inspect type "Code" after r3_editor_run to see whether your scripts run cleanly; null means the tab does not report them.

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>"
    },
    "name": "r3_editor_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoComponent ids to read.
typeNoOnly components of this type, e.g. "Mesh" or "R3ComponentMesh".
fieldsNoOnly these properties, e.g. ["position", "rotation"].
entityRefNoOnly the component with this entityRef.
projectIdYesThe project, open in the user's editor.

Output Schema

NameRequiredDescriptionDefault
liveYes
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
projectIdYes
componentsYes
unreadableYes
projectNameYes
fieldsNotFoundYes
scriptDiagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / scriptDiagnostics
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "at": {
      +            "type": "string"
      +          },
      +          "componentId": {
      +            "type": "string"
      +          },
      +          "count": {
      +            "type": "number"
      +          },
      +          "entityRef": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "fileName": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "kind": {
      +            "enum": [
      +              "error",
      +              "warning"
      +            ],
      +            "type": "string"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "componentId",
      +          "entityRef",
      +          "fileName",
      +          "kind",
      +          "name",
      +          "message",
      +          "at",
      +          "count"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "projectName",
      -  "live",
      -  "components",
      -  "unreadable",
      -  "fieldsNotFound",
      -  "editor",
      -  "answer"
      -]New value: +[
      +  "projectId",
      +  "projectName",
      +  "live",
      +  "components",
      +  "unreadable",
      +  "fieldsNotFound",
      +  "scriptDiagnostics",
      +  "editor",
      +  "answer"
      +]
  2. 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"
      +  }
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / components / items / properties / eventName
      Added value: +{
      +  "type": "string"
      +}
  4. 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",
      -  "projectName",
      -  "live",
      -  "components",
      -  "unreadable",
      -  "fieldsNotFound",
      -  "editor"
      -]New value: +[
      +  "projectId",
      +  "projectName",
      +  "live",
      +  "components",
      +  "unreadable",
      +  "fieldsNotFound",
      +  "editor",
      +  "answer"
      +]
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds real context beyond the annotations: it requires a tab with the project open, enforces a 50-component cap with an explanatory refusal, states the return shape matches r3_component_read so results can be fed to r3_component_set, and explains that scriptDiagnostics can be null when the tab doesn't report them. The read-only claim is consistent with readOnlyHint and with idempotentHint=false, since live values move between 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?

Well front-loaded — the live-read distinction comes first, then selection parameters, then limits, then diagnostics. It loses a point for repeating the open-tab prerequisite twice in near-identical phrasing.

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?

Covers everything an agent needs for a 5-parameter live-inspection tool: the tab prerequisite, how selectors combine, the result cap, output shape compatibility, and the diagnostics field's null semantics, even though an output schema also exists.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: ids, type and entityRef combine as a conjunction, and fields is a projection that keeps only named properties. The 50-component ceiling on the combined result is also new information.

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 and resource — reading what components hold RIGHT NOW, including runtime values of a moving body while the project runs — and explicitly contrasts it with r3_component_read, which returns kept values without a tab.

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?

Gives concrete when-to-use guidance (debug live behaviour, inspect type "Code" after r3_editor_run) and names the alternatives with the condition selecting them: r3_editor_open to open a tab, r3_component_read when no live tab is needed.

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