Skip to main content
Glama

filesystem_manage

Read, write, list, move, delete, and scan Godot project files; reimport and download assets to keep the editor filesystem in sync.

Instructions

Project filesystem access via the Godot editor's EditorFileSystem.

Ops: • read_text(path) Read a text file at a res:// path. Returns content, size, line_count. • write_text(path, content="") Create or overwrite a text file. Updates the editor filesystem entry for that one file (single-file update, not a full scan). Newly-created files include data.cleanup.rm for transient smoke tests; overwrite omits the field. • reimport(paths) Force-reimport the listed files via EditorFileSystem.update_file. paths is a list of res:// paths. Intended for imported assets such as textures, models, and audio. Paths that are not imported resources (.gd scripts, .tscn, hand-written .tres, or an asset the editor has not imported yet) report under skipped_non_imported rather than reimported: their filesystem entry is refreshed, but no import runs, so a success there is not evidence that a script parsed or that diagnostics were produced. Use script_patch/script_create to save a script and receive fresh diagnostics, or scan for an asset awaiting its first import. Returns reimported, skipped_non_imported, not_found and their counts. • list(path="res://", recursive=False, max_depth=1) Browse the project's res:// tree (files, sizes, UIDs, and directories). • delete(path) Delete a file or directory from the project along with its .uid and .import sidecars. • move(from_path, to_path) Move or rename a file in the project, keeping sidecars consistent. • scan() Force a full EditorFileSystem.scan() and wait for it to settle. This is the headless equivalent of the editor regaining window focus: write_text/script_create register single files but do NOT rebuild the global class_name table, so a freshly-created class_name MyThing extends Resource is invisible to resource_manage/type references until a scan runs. Call this once after adding class_name scripts when the editor isn't focused. Single-flight (awaits any in-progress scan rather than stacking another). Returns scan_completed and global_classes_registered_delta. • search(name="", type="", path="", offset=0, limit=100) Find files by name, resource type, or path substring. At least one filter must be set. Paginated. • download_and_import(url, dest="", path="", extract=False, filter="", reimport=True) Download an asset or archive, optionally unpack, configure filter ("nearest" for pixel art), and trigger Godot reimport and scan. • download_asset(url, path="", dest="", extract=False, filter="", reimport=True) Download an asset or zip archive from the internet directly into the Godot project (res:// path). If extract=True or archive is zip, extracts into target directory. Automatically triggers editor reimport and scan. Returns: {url, path, size_bytes, is_archive, extracted_files, filter_applied} • search_assets(query="", category="all", limit=20) Search curated free/CC0 game assets (tilesets, audio, textures, UI, 3D models). Categories: "all", "tileset", "audio", "texture", "ui". Returns matching assets with direct download URLs ready for download_asset.

Canonical call shape: {"op": "<verb>", "params": {...}}. Flat op parameters are accepted as a compatibility alias when the client transmits them; op and session_id remain top-level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYes
paramsNo
session_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.28
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "asset_search",
      -  "delete",
      -  "download_and_import",
      -  "download_asset",
      -  "download_file",
      -  "list",
      -  "move",
      -  "read_text",
      -  "reimport",
      -  "scan",
      -  "search",
      -  "search_assets",
      -  "write_text"
      -]New value: +[
      +  "asset_search",
      +  "delete",
      +  "delete_file",
      +  "download_and_import",
      +  "download_asset",
      +  "download_file",
      +  "list",
      +  "list_dir",
      +  "list_files",
      +  "ls",
      +  "move",
      +  "move_file",
      +  "read",
      +  "read_file",
      +  "read_text",
      +  "reimport",
      +  "scan",
      +  "search",
      +  "search_assets",
      +  "tree",
      +  "write",
      +  "write_file",
      +  "write_text"
      +]
  2. Changed1 schema field changedv5.0.14
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "asset_search",
      -  "delete",
      -  "download_asset",
      -  "download_file",
      -  "list",
      -  "move",
      -  "read_text",
      -  "reimport",
      -  "scan",
      -  "search",
      -  "search_assets",
      -  "write_text"
      -]New value: +[
      +  "asset_search",
      +  "delete",
      +  "download_and_import",
      +  "download_asset",
      +  "download_file",
      +  "list",
      +  "move",
      +  "read_text",
      +  "reimport",
      +  "scan",
      +  "search",
      +  "search_assets",
      +  "write_text"
      +]
  3. Changed1 schema field changedv5.0.9
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "read_text",
      -  "reimport",
      -  "scan",
      -  "search",
      -  "write_text"
      -]New value: +[
      +  "asset_search",
      +  "delete",
      +  "download_asset",
      +  "download_file",
      +  "list",
      +  "move",
      +  "read_text",
      +  "reimport",
      +  "scan",
      +  "search",
      +  "search_assets",
      +  "write_text"
      +]
  4. First observedv4.1.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries full responsibility for behavior disclosure. It is exceptionally transparent: it details side effects (write_text adds data.cleanup.rm for new files), scope of updates (single-file vs full scan), return structures, and caveats (reimport on non-imported resources does not prove parsing). It even explains the headless scan behavior and single-flight semantics. No behavioral traits are hidden.

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?

Although the description is long, it is well-structured: an opening summary, a bulleted list of operations with consistent formatting, and a closing note on call shape. Each sentence carries essential information—no filler. The information is front-loaded with the purpose, and the detailed operation blocks are logically ordered. The length is justified by the tool's multi-op nature.

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?

The description is complete for a complex multi-op tool. It covers every operation's parameters, return values, side effects, and edge cases. It even addresses when a full scan is needed versus single-file updates, and how to interpret results (e.g., skipped_non_imported). Given that an output schema exists but the description provides per-op return details, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema coverage is 0% (no descriptions in schema), so the description must compensate. It does so comprehensively: each operation lists its parameters with types, defaults, and meaning (e.g., read_text(path), write_text(path, content=''), reimport(paths), list(path, recursive, max_depth)). It also describes the canonical call shape and accepts aliases. This fully bridges the gap left by the schema.

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 clearly states the tool's purpose: 'Project filesystem access via the Godot editor's EditorFileSystem.' It lists specific operations (read, write, reimport, list, delete, move, scan, search, download, etc.) with a clear verb+resource structure. It distinguishes itself from sibling tools by focusing on the filesystem layer, and it names alternatives within the tool (e.g., script_patch/script_create for diagnostics).

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?

The description provides explicit guidance on when to use each operation and when to prefer alternatives. For example, reimport notes that non-imported resources are skipped and recommends script_patch/script_create for scripts, and scan for assets awaiting first import. It also explains when a full scan is necessary (after adding class_name scripts) versus single-file updates. This internal guidance helps agents choose correctly without external references.

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