Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_script_dependencies

Retrieve all resources and scripts that a given Godot script depends on by providing its res:// path, so you can inspect dependencies before editing or refactoring.

Instructions

Get all resources and scripts that a given script depends on.

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": {
      "script_path": "<script_path>"
    },
    "name": "get_script_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
script_pathYesres:// path to the script

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, but it only says what is fetched. It does not disclose whether dependencies are direct or transitive (recursive), how missing/broken references are handled, or whether the result includes only res:// paths.

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?

One short, front-loaded sentence with no wasted words. It is efficient though minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the definition is minimally adequate, but it leaves the return shape (dependency list format) and the direct-vs-transitive scope unexplained.

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% and the single script_path parameter is already documented as a res:// path, so the description adds nothing beyond the schema. Baseline 3 applies when the schema does the work.

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 specific verb and resource: retrieves the resources and scripts a given script depends on. That is clearly distinct from the sibling detect_circular_dependencies, but the description does not explicitly name or differentiate against it.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives. It doesn't state prerequisites, e.g. whether the script must exist or be open, nor does it point to detect_circular_dependencies or read_script for related needs.

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

Deploy Server

Other Tools