Skip to main content
Glama

batch_scene_operations

Destructive

Run multiple scene mutations (add nodes, load sprites, set properties, save scenes) in one process, saving each mutated scene at the end. Use instead of chaining single tools, with abort-on-error control.

Instructions

Run several scene mutations in one process; every mutated scene is saved at the end. Use instead of chaining add_node, load_sprite, set_node_properties or save_scene. Each item sets operation (save stands for save_scene) and takes that tool's params. abortOnError stops at the first failure; later items return skipped: true. Returns: results[] in input order: operation, scenePath, success, error or skipped, plus the operation's own fields. Errors while a runtime session is live on this project.

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>",
      "operations": "<operations>"
    },
    "name": "batch_scene_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationsYesOrdered list of scene operations. Each item has its own operation and scenePath.
projectPathYesPath to the Godot project directory
abortOnErrorNoStop processing on first error (default: false)

Output Schema

NameRequiredDescriptionDefault
resultsYes
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv4.0.1
    • changedInput schema / properties / operations / items / properties / operation / description
      Previous value: -"The sub-operation to perform"New value: +"Required. The sub-operation to perform"
    • changedInput schema / properties / operations / items / properties / rotation / description
      Previous value: -"[add_node] Rotation in radians - shorthand for properties.rotation"New value: +"[add_node] Rotation in radians on a 2D node - shorthand for properties.rotation. A 3D node takes {\"x\",\"y\",\"z\"} under properties.rotation"
    • changedInput schema / properties / operations / items / properties / scale / description
      Previous value: -"[add_node] Vector2 scale - shorthand for properties.scale"New value: +"[add_node] Scale - {\"x\",\"y\"} for 2D nodes, {\"x\",\"y\",\"z\"} for 3D. Shorthand for properties.scale"
    • addedOutput schema / properties / results / items / properties / nodeName
      Added value: +{
      +  "description": "[add_node] Name after the add.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / nodePath
      Added value: +{
      +  "description": "[add_node, load_sprite]",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / nodeType
      Added value: +{
      +  "description": "[add_node, load_sprite]",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / savedScenePath
      Added value: +{
      +  "description": "[save] The file written.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / skipped
      Added value: +{
      +  "description": "True when abortOnError stopped the batch before this operation ran.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / results / items / properties / texturePath
      Added value: +{
      +  "description": "[load_sprite]",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / updates
      Added value: +{
      +  "description": "[set_node_properties] One entry per update, in input order.",
      +  "items": {
      +    "properties": {
      +      "error": {
      +        "type": "string"
      +      },
      +      "nodePath": {
      +        "type": "string"
      +      },
      +      "property": {
      +        "type": "string"
      +      },
      +      "resolvedNodePath": {
      +        "description": "Where nodePath led, in root/... form. Present when the node was found; differs from nodePath for a %Name path.",
      +        "type": "string"
      +      },
      +      "skipped": {
      +        "description": "True when abortOnError stopped this operation before this update.",
      +        "type": "boolean"
      +      },
      +      "success": {
      +        "type": "boolean"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "results"
      +]
  2. Changed1 schema field changedv3.8.0
    • changedInput schema / properties / operations / items / properties / updates / items / properties / value / description
      Previous value: -"New value. Vector2/Vector3/Color auto-convert from {\"x\",\"y\"} / {\"x\",\"y\",\"z\"} / {\"r\",\"g\",\"b\",\"a\"} objects; primitives pass through"New value: +"New value. Vector2/Vector3/Color auto-convert from {\"x\",\"y\"} / {\"x\",\"y\",\"z\"} / {\"r\",\"g\",\"b\",\"a\"} objects; primitives pass through. For Packed*Array properties, a plain array applies the same conversions element-wise (e.g. [{\"x\":10,\"y\":20}, ...] for Polygon2D.polygon); an element that cannot represent the packed element type errors instead of silently storing zeros."
  3. Changed5 schema fields changedv3.6.0
    • changedInput schema / properties / operations / items / properties / modulate / description
      Previous value: -"[add_node] Color modulation — shorthand for properties.modulate"New value: +"[add_node] Color modulation - shorthand for properties.modulate"
    • changedInput schema / properties / operations / items / properties / position / description
      Previous value: -"[add_node] Position — {\"x\",\"y\"} for 2D nodes, {\"x\",\"y\",\"z\"} for 3D. Shorthand for properties.position"New value: +"[add_node] Position - {\"x\",\"y\"} for 2D nodes, {\"x\",\"y\",\"z\"} for 3D. Shorthand for properties.position"
    • changedInput schema / properties / operations / items / properties / rotation / description
      Previous value: -"[add_node] Rotation in radians — shorthand for properties.rotation"New value: +"[add_node] Rotation in radians - shorthand for properties.rotation"
    • changedInput schema / properties / operations / items / properties / scale / description
      Previous value: -"[add_node] Vector2 scale — shorthand for properties.scale"New value: +"[add_node] Vector2 scale - shorthand for properties.scale"
    • changedInput schema / properties / operations / items / properties / visible / description
      Previous value: -"[add_node] Visibility — shorthand for properties.visible"New value: +"[add_node] Visibility - shorthand for properties.visible"
  4. Changed3 schema fields changedv3.5.0
    • addedInput schema / properties / operations / items / properties / abortOnError
      Added value: +{
      +  "description": "[set_node_properties] Stop processing on first error",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / operations / items / properties / operation / enum
      Previous value: -[
      -  "add_node",
      -  "load_sprite",
      -  "save"
      -]New value: +[
      +  "add_node",
      +  "load_sprite",
      +  "set_node_properties",
      +  "save"
      +]
    • addedInput schema / properties / operations / items / properties / updates
      Added value: +{
      +  "description": "[set_node_properties] Property updates to apply in this operation",
      +  "items": {
      +    "properties": {
      +      "nodePath": {
      +        "description": "Node path from scene root",
      +        "type": "string"
      +      },
      +      "property": {
      +        "description": "Property name in snake_case",
      +        "type": "string"
      +      },
      +      "value": {
      +        "description": "New value. Vector2/Vector3/Color auto-convert from {\"x\",\"y\"} / {\"x\",\"y\",\"z\"} / {\"r\",\"g\",\"b\",\"a\"} objects; primitives pass through"
      +      }
      +    },
      +    "required": [
      +      "nodePath",
      +      "property",
      +      "value"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  5. Changed5 schema fields changedv3.3.0
    • addedInput schema / properties / operations / items / properties / modulate
      Added value: +{
      +  "description": "[add_node] Color modulation — shorthand for properties.modulate",
      +  "type": "object"
      +}
    • addedInput schema / properties / operations / items / properties / position
      Added value: +{
      +  "description": "[add_node] Position — {\"x\",\"y\"} for 2D nodes, {\"x\",\"y\",\"z\"} for 3D. Shorthand for properties.position",
      +  "type": "object"
      +}
    • addedInput schema / properties / operations / items / properties / rotation
      Added value: +{
      +  "description": "[add_node] Rotation in radians — shorthand for properties.rotation",
      +  "type": "number"
      +}
    • addedInput schema / properties / operations / items / properties / scale
      Added value: +{
      +  "description": "[add_node] Vector2 scale — shorthand for properties.scale",
      +  "type": "object"
      +}
    • addedInput schema / properties / operations / items / properties / visible
      Added value: +{
      +  "description": "[add_node] Visibility — shorthand for properties.visible",
      +  "type": "boolean"
      +}
  6. Addedv3.1.1
  7. Removedv3.0.0
  8. Addedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only supply destructiveHint=true, so the description carries most of the weight and does it well: it discloses that all mutated scenes get saved at the end, that abortOnError halts at the first failure, and that later items return skipped: true. The final sentence, 'Errors while a runtime session is live on this project', is grammatically broken and leaves the runtime-session constraint ambiguous, which is the main gap.

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 most important facts — batching, end-of-run save, and substitute-for-chaining — are front-loaded in the first two sentences. The return-format sentence is dense but useful; however, the trailing 'Errors while a runtime session is live on this project' is a fragment that reads as truncated and slightly undercuts the otherwise clean structure.

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

Completeness4/5

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

For a nested batch tool that mutates and saves project files, the description covers the destructive behavior, error-handling mode, and result ordering. With an output schema present the explicit return-field listing is somewhat redundant, and the vague runtime-session caveat is the one place an agent could still be surprised.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: it explains that each array item carries its own 'operation' and 'scenePath' and takes that sub-tool's parameters, and clarifies that 'save' stands for save_scene. It also defines the top-level abortOnError default behavior, which the schema states only tersely.

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 opens with a specific verb and resource: 'Run several scene mutations in one process', and immediately discloses the implicit save semantics ('every mutated scene is saved at the end'). It explicitly distinguishes the tool from the single-operation siblings, so an agent can identify its role without opening the schema.

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?

It names the exact alternatives it replaces ('Use instead of chaining add_node, load_sprite, set_node_properties or save_scene') and the condition that selects it (multiple mutations batched together). The mapping of each item's 'operation' to the corresponding single tool reinforces which path to take per operation.

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