Skip to main content
Glama

scene_outline

Read-only

Reads the actor hierarchy from a saved .scene or .prefab file on disk so you can inspect its structure and scripts without relying on unsaved editor changes.

Instructions

Reads the actor tree of a saved .scene or .prefab file on disk. The tree comes from the ParentID links, not from the file order. The scripts of an actor are in its Scripts list, not in its child nodes. Truncated is true when the tool reached the depth or node limit. The tool does not see unsaved changes. For the live tree in the running editor, use editor_scene_graph.

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": {
      "path": "<path>"
    },
    "name": "scene_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
idYes
rootsYes
truncatedYes
engineBuildYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses non-obvious semantics: hierarchy is derived from ParentID links rather than file order, scripts live in an actor's Scripts list rather than child nodes, and 'Truncated' signals a depth/node limit was hit. These are exactly the behavioral traits an agent cannot infer from annotations.

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?

Five short sentences, each contributing distinct information, with the core purpose front-loaded and the sibling routing held for last. No filler or restatement of the tool name.

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-value documentation is unnecessary, and the description covers data provenance, truncation, and staleness well. The only gap is that the 'depth or node limit' is referenced without explanation and no such limit is exposed as a parameter, leaving the truncation behavior slightly ambiguous.

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 0% for the single 'path' parameter, so the description carries the burden. It implies the argument points at a saved .scene or .prefab on disk, but does not specify whether the path is absolute, project-relative, or what extension/format rules apply.

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?

The first sentence names a specific verb and resource ('Reads the actor tree of a saved .scene or .prefab file on disk') and the final sentence explicitly separates it from the sibling editor_scene_graph (live tree). An agent can distinguish the two tools without inspecting either schema.

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

Usage Guidelines4/5

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

It names the alternative (editor_scene_graph) and the condition selecting it ('live tree in the running editor'), and warns that unsaved changes are invisible, which implies saving is a prerequisite. No further exclusions or caveats are given, so it falls short of a full when/when-not treatment.

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