Skip to main content
Glama

save_scene

Idempotent

Saves a re-packed Godot scene to disk, either overwriting the original or writing a save-as copy to a new path, and warns when content was dropped during the save.

Instructions

Re-pack and save a scene, optionally to another path (save-as). The mutation tools save by themselves: use this only for save-as via newPath, or to re-canonicalize a hand-edited .tscn. Overwrites silently. A newPath file gets no uid of its own. Returns: scenePath (loaded) and savedScenePath (written, confirmed on disk); warnings leads if the save dropped content. 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>",
      "scenePath": "<scenePath>"
    },
    "name": "save_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
newPathNoSave to a different path (relative to project) instead of overwriting the original
scenePathYesScene file path relative to the project
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
warningsNo
scenePathYesThe scene that was loaded.
savedScenePathYesThe file that was written. Equal to scenePath unless newPath was given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "savedScenePath": {
      +      "description": "The file that was written. Equal to scenePath unless newPath was given.",
      +      "type": "string"
      +    },
      +    "scenePath": {
      +      "description": "The scene that was loaded.",
      +      "type": "string"
      +    },
      +    "warnings": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "scenePath",
      +    "savedScenePath"
      +  ],
      +  "type": "object"
      +}
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Addedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply idempotentHint, so the description carries the rest and does so: silent overwrite, no uid generated for a newPath file, warning leads when content is dropped, and an error condition when a runtime session is live. These are consequences an agent could not infer from the schema or annotations.

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?

Front-loaded with purpose and the use-case restriction, and nearly every clause carries new information. Some sentences are clipped to the point of awkwardness ('warnings leads if the save dropped content'), which costs a little readability.

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?

Covers the decisions an agent must make (when to call it, overwrite behavior, save-as side effects, live-session failure) and even names the returned paths despite an output schema existing. Nothing needed to invoke it correctly is missing.

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; the description still adds meaning by framing newPath as save-as and noting the resulting file gets no uid of its own. It does not elaborate on projectPath or path resolution beyond what the schema says.

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?

States a specific verb and resource ('Re-pack and save a scene') plus the key variation ('optionally to another path (save-as)'). It also distinguishes itself from the mutation tools that save automatically, so an agent can tell exactly what this tool is for.

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?

Gives an explicit when-not ('The mutation tools save by themselves') and narrows its own use to two cases: save-as via newPath, or re-canonicalizing a hand-edited .tscn. That is a clear routing rule rather than implied usage.

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