Skip to main content
Glama

get_scene_dependencies

Read-only

Parse a .tscn file to list external resource dependencies (scripts, textures, subscenes) before refactoring or moving files, helping avoid broken references.

Instructions

Parse a .tscn file for ext_resource references (scripts, textures, subscenes). Use to see what a scene depends on before refactoring or moving files. Returns: scenePath and dependencies[], one per ext_resource reference (path, type, optional uid). warnings leads when ext_resource lines could not be read. Errors if the file does not exist or is not a text scene or resource.

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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>"
    },
    "name": "get_scene_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenePathYesPath to the .tscn file relative to the project root (e.g. "scenes/main.tscn")
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
warningsNo
scenePathYes
dependenciesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.0.1
    • removedOutput schema / properties / scene
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / scenePath
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "scenePath",
      +  "dependencies"
      +]
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Addedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description adds real behavior beyond that: partial-failure handling ("warnings leads when ext_resource lines could not be read") and hard error conditions (missing file, non-text scene). Those are exactly the traits an agent needs to interpret odd results without extra 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?

Four compact sentences that lead with what is parsed, then when to use it, then output and failure behavior — no filler. The "Returns:" sentence is partly redundant given an output schema exists, which keeps it off a perfect score.

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?

For a two-parameter read-only parser with 100% schema coverage and an output schema, everything an agent needs is present: scope, dependency types found, warnings-first behavior, and error cases. Nothing material is left to inference.

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 coverage is 100%, so both projectPath and scenePath are already documented in the schema, and the description adds little parameter-specific meaning beyond reinforcing that the input is a .tscn path. Baseline 3 is appropriate when the schema carries the parameter burden.

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 description pairs a specific verb ("Parse") with a specific resource (a .tscn file) and names the exact artifact it extracts (ext_resource references for scripts, textures, subscenes). That framing makes it distinguishable from hierarchy-oriented siblings such as get_scene_tree, since the agent knows this covers dependencies rather than nodes.

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?

"Use to see what a scene depends on before refactoring or moving files" gives a concrete triggering situation, which is more than implied usage. It stops short of the top score because it names no alternative tool or explicit when-not condition (e.g. preferring get_scene_tree when node structure is the question).

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