Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_filesystem_tree

Retrieve the project filesystem tree from a specified root path and optional depth limit, helping inspect Godot project structure for AI-driven development.

Instructions

Get the filesystem tree of the project starting at the given path.

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": "get_filesystem_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoRoot path to list (default: res://)
max_depthNoMaximum depth to traverse

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. 'Get' implies read-only, but it says nothing about traversal defaults (what depth is used if max_depth is omitted), whether hidden/imported files are included, how large the response may be for a deep project, or the shape of the returned tree.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity leaves required behavioral detail to other dimensions rather than earning extra credit here.

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

Completeness2/5

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

A two-parameter traversal tool with no annotations and no output schema needs the description to explain what the tree output looks like and how depth affects it. Neither is covered, leaving an agent unable to predict response size or recursion behavior before calling.

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 parameters are already documented including the res:// default for path. The description only restates that traversal starts at 'the given path' and adds no meaning beyond the schema, so the baseline 3 applies.

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?

Specific verb ('Get') and resource ('filesystem tree of the project') with a stated starting point. It implicitly distinguishes itself from scene-tree siblings by saying 'filesystem', but never names them or states the distinction explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the resource name: an agent can infer 'I need to explore project files' but the description gives no when-to-use/when-not and no reference to the scene-tree alternatives that could easily be confused with this one.

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