Skip to main content
Glama

Resource Manage

resource_manage

Find, inspect, assign, and create Godot resources—from curves and textures to physics shapes and SpriteFrames—without leaving the live editor.

Instructions

Resource (asset) search, inspection, assignment, and creation. Covers generic Resource subclasses plus specialized authoring (Curve, Environment, physics shapes, gradient/noise textures).

Ops: • search(type="", path="", offset=0, limit=100) Search for resources by type or path. Type matching includes subclasses. At least one filter required. Paginated. • load(path) Inspect a .tres / .res — returns type and editor-visible properties. • inspect(node_path, property, depth=2) Read a live native resource graph without loading or modifying files. Depth 0..3; shared references, omission reasons, fixed traversal and 64 KiB encoded-result limits. Scripted/dynamic properties excluded. • assign(path, property, resource_path) Load and assign a resource to a node property. Undoable. • get_info(type) Introspect a Resource class — properties, parent, abstract flag, concrete_subclasses (for abstract bases). Read-only. • create(type, properties=None, path="", property="", resource_path="", overwrite=False) Instantiate a Resource subclass. Either path+property (assign to a node, undoable) or resource_path (save to .tres). For specific families (Curve, Environment, etc.) prefer the dedicated ops. Inline {"class": ...} constructors require Resource-typed slots or typed Resource collections. Untyped collections that discard a nested constructor are refused before saving or assigning. PackedByteArray properties accept lists of whole numbers 0..255, at most 65,536 bytes per value; [] clears. • sprite_frames_create(resource_path, animations, overwrite=False) Build saved SpriteFrames with native animations and textures. animations: [{"name":"walk","fps":8,"loop_mode":"linear","frames":[ {"texture_path":"res://sheet.png","region":{"x":0,"y":0, "width":16,"height":16},"duration":1}]}]. Omit region for a whole texture; otherwise an AtlasTexture is built explicitly. loop_mode is none, linear, or pingpong. At most 4096 animations/total frames. Unknown fields and invalid regions fail before saving. Persistent, not scene-undoable; overwrite replaces the whole resource, retaining UID. • set_properties(path, properties) Patch an existing non-imported res:// .tres/.res without resetting omitted values. Refreshes held references while preserving identity and UID. Engine built-in resources only, including nested resources. Custom scripts, GDExtension resources and resource cycles are refused. Persistent file edit, not scene-undoable. Validation/staging failures leave the original unchanged. Windows replacement retains a backup; it is not crash-atomic. Failed restoration reports recovery_backup and staged_resource paths. A rare post-save refresh failure reports disk_committed=true explicitly. • curve_set_points(points, path="", property="", resource_path="") Replace all points on a Curve / Curve2D / Curve3D. Auto-creates the curve resource if the slot is empty (curve_created flag). • environment_create(path="", preset="default", properties=None, sky=None, resource_path="", overwrite=False) Build Environment + Sky chain. Presets: default | clear | sunset | night | fog. sky may be bool or a procedural sky dict such as {"sky_material": "procedural", "sky_top_color": "#0f172a"}. Either assign to a WorldEnvironment node or save .tres. • physics_shape_autofit(path, source_path="", shape_type="") Size a CollisionShape2D/3D to a nearby visual's bounds. Searches direct siblings then parent-siblings (handles nested Body→Collision layouts). Ambiguous matches return candidate paths in error.data.candidates. Auto-creates the concrete Shape subclass if needed. shape_type accepts either the short form ("box", "sphere", "capsule", "cylinder" for 3D; "rectangle", "circle", "capsule" for 2D) or the matching Godot class name ("BoxShape3D", "RectangleShape2D", etc.). • physics_shape_generate(paths, shape_type="box", body_type="static", reparent_mesh=False, scene_file="", overwrite=False) Generate a physics body sibling (named Collider) with a CollisionShape3D for every MeshInstance3D path. Shapes are fitted in body-local space; a mesh that already has a collider sibling, a duplicate path, or a scene-root mesh is refused before anything is written. shape_type: auto | box | sphere | capsule | cylinder | convex | trimesh (or the class name for explicit shapes). Opt-in auto selects matching primitives for BoxMesh, SphereMesh, CapsuleMesh and CylinderMesh, with box bounds for every other mesh. The default remains box. Auto uses bounding fits (including tapered cylinders), not exact mesh geometry. convex/trimesh derive the shape from the mesh's own triangles, with the mesh scale baked into the shape, and are limited to 2048 triangles and 6144 vertices per mesh, with bounded mesh types (the hull build runs synchronously inside one editor-frame item); trimesh needs a static or area body, and a non-uniformly scaled parent chain refuses every type except box. body_type: static | area | rigid | character. rigid/character always wrap the mesh under the generated body (a detached dynamic body would fall away from the stationary visual); reparent_mesh=True does the same for static/area while preserving the mesh's world transform, and the reported mesh_path is then the post-move path. overwrite=True refreshes only a marked generated collider's shape and collision transform, preserving body/collision identity and user settings. Requested body type and wrapping must match; unmarked legacy bodies or broken provenance links are refused. Mixed fresh/refresh batches prepare all resources before one undo action; stale edits refuse the batch. scene_file pins the request to that edited scene. Up to 1024 paths are processed in bounded work across editor frames; inside batch_execute at most 16. The bulk write is one undo action. Returns: {created: [{mesh_path, body_path, shape_path, shape_type, body_type, operation: "create"|"refresh"}], undoable: true}. • gradient_texture_create(stops, width=256, height=1, fill="linear", path="", property="", resource_path="", overwrite=False) Build GradientTexture2D from color stops. fill: linear | radial | square. • noise_texture_create(noise_type="simplex_smooth", width=512, height=512, frequency=0.01, seed=0, fractal_octaves=0, path="", property="", resource_path="", overwrite=False) Build NoiseTexture2D wrapping FastNoiseLite. Noise types: simplex | simplex_smooth | perlin | cellular | value | value_cubic.

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.

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": {
      "op": "<op>"
    },
    "name": "resource_manage"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYes
paramsNo
session_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.4.1
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "assign",
      -  "create",
      -  "curve_set_points",
      -  "environment_create",
      -  "get_info",
      -  "gradient_texture_create",
      -  "inspect",
      -  "load",
      -  "noise_texture_create",
      -  "physics_shape_autofit",
      -  "physics_shape_generate",
      -  "search"
      -]New value: +[
      +  "assign",
      +  "create",
      +  "curve_set_points",
      +  "environment_create",
      +  "get_info",
      +  "gradient_texture_create",
      +  "inspect",
      +  "load",
      +  "noise_texture_create",
      +  "physics_shape_autofit",
      +  "physics_shape_generate",
      +  "search",
      +  "set_properties",
      +  "sprite_frames_create"
      +]
  2. Changed1 schema field changedv4.2.1
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "assign",
      -  "create",
      -  "curve_set_points",
      -  "environment_create",
      -  "get_info",
      -  "gradient_texture_create",
      -  "load",
      -  "noise_texture_create",
      -  "physics_shape_autofit",
      -  "physics_shape_generate",
      -  "search"
      -]New value: +[
      +  "assign",
      +  "create",
      +  "curve_set_points",
      +  "environment_create",
      +  "get_info",
      +  "gradient_texture_create",
      +  "inspect",
      +  "load",
      +  "noise_texture_create",
      +  "physics_shape_autofit",
      +  "physics_shape_generate",
      +  "search"
      +]
  3. Changed1 schema field changedv4.0.3
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "assign",
      -  "create",
      -  "curve_set_points",
      -  "environment_create",
      -  "get_info",
      -  "gradient_texture_create",
      -  "load",
      -  "noise_texture_create",
      -  "physics_shape_autofit",
      -  "search"
      -]New value: +[
      +  "assign",
      +  "create",
      +  "curve_set_points",
      +  "environment_create",
      +  "get_info",
      +  "gradient_texture_create",
      +  "load",
      +  "noise_texture_create",
      +  "physics_shape_autofit",
      +  "physics_shape_generate",
      +  "search"
      +]
  4. Addedv3.1.4
  5. Removedv3.0.7
  6. First observedv2.9.1

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so in depth: it distinguishes undoable scene edits (assign, physics_shape_generate's single undo action) from persistent file writes (set_properties, sprite_frames_create), and discloses concrete limits (64 KiB encoded inspect result, 4096 animations, 2048 triangles / 6144 vertices, 1024 paths, 16 inside batch_execute). Failure semantics are unusually well covered, including error.data.candidates, recovery_backup/staged_resource paths, the disk_committed flag, and the caveat that Windows replacement is not crash-atomic.

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?

The summary line is front-loaded and each op is a clearly labeled bullet, which is the right structure for a 14-op dispatcher. Some entries are dense walls of text — physics_shape_generate in particular runs long and mixes refusal rules, limits, and return shape in one block — but almost every sentence conveys operational fact rather than filler.

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 high-complexity multi-op tool with a thin envelope schema, the description supplies everything an agent needs: dispatch shape, per-op parameters, mutation-vs-persistent behavior, limits, and failure reporting. An output schema exists, and the one op with non-obvious returns (physics_shape_generate) still spells out its result object.

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?

Schema description coverage is 0% — the schema is only an op/params/session_id envelope — so the description must supply all per-op meaning, and it does: defaults, valid enum values (loop_mode none/linear/pingpong, fill linear/radial/square, shape_type short forms vs Godot class names, noise types), nested structures (animations/frames/region), and edge semantics such as '[] clears' for PackedByteArray. It even documents the canonical {op, params} call shape and the flat-parameter compatibility alias.

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?

Opens with a specific verb+resource framing ('Resource (asset) search, inspection, assignment, and creation') and enumerates all 14 operations with signatures, so the scope is unambiguous. It does not, however, differentiate itself from siblings like material_manage, theme_manage, or particle_manage, which also create Resource subclasses — an agent must infer the boundary.

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?

Nearly every op carries a when/which clause: 'At least one filter required' for search, 'For specific families (Curve, Environment, etc.) prefer the dedicated ops' for create, and 'Either path+property ... or resource_path' for the creation ops. Exclusions are explicit (set_properties refuses custom scripts, GDExtension resources and cycles; physics_shape_generate refuses duplicate paths and scene-root meshes). It stops short of stating when to pick this tool over a sibling manager.

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