Skip to main content
Glama

editor_scene_graph

Read-only

Returns the live actor tree of every open scene in the running Flax Editor, including unsaved changes, for inspecting scene structure while the editor is active.

Instructions

Returns the live actor tree of every scene that is open in the running Flax Editor, with the unsaved changes. Truncated is true when the tree has more than 500 nodes or 32 levels. For a saved .scene or .prefab file without the editor, use scene_outline. To find actors by name or type, use editor_find_actors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "editor_scene_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
scenesYes
truncatedYes
mainThreadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that — the tree reflects live, unsaved editor state, and results are truncated above 500 nodes or 32 levels with 'Truncated' set true. It does not discuss cost or latency for very large scenes, which is the only remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core behavior, then the truncation limits, then routing to alternatives. Every sentence carries distinct information with no waste.

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?

An output schema exists, so return-shape detail is unnecessary, and with no parameters the description's only job is scope, truncation, and sibling routing — all of which are covered. Nothing an agent needs to invoke it correctly is missing.

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?

The tool has zero parameters, so there is nothing to disambiguate and no schema burden to compensate for. The description correctly spends no words on parameters; the baseline of 4 applies.

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 ('Returns the live actor tree of every scene') plus a scope qualifier ('open in the running Flax Editor, with the unsaved changes'). It immediately differentiates from scene_outline (saved files, no editor) and editor_find_actors (search by name/type), so an agent can select it without opening a 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?

Explicitly names both alternatives and the conditions that select them: use scene_outline for a saved .scene/.prefab without the editor, and editor_find_actors to find actors by name or type. This tool is left as the choice for the live, in-editor, unsaved state.

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