Gear

Overview Schema Source Related Servers Discussions Admin

scene-save

Save changes to a Godot scene file or create a variant at a new path. Use for explicit saves or creating scene variants.

Instructions

[compact alias of save_scene] Saves changes to a scene file or creates a variant at a new path. Most scene modification tools save automatically, but use this for explicit saves or creating variants.

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": "scene-save"
  }
}

Input Schema

Name	Required	Description
`projectPath`	Yes	Absolute path to project directory containing project.godot. Use the same path across all tool calls in a workflow.
`scenePath`	Yes	Path to .tscn file relative to project (e.g., "scenes/Player.tscn")
`newPath`	No	Optional: New path to save as variant (e.g., "scenes/PlayerBlue.tscn")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Describes behavior (saving, creating variants) adequately. No annotations exist, so description carries full burden. Could mention overwrite behavior but overall sufficient.

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?

Two sentences, every word earns its place: first defines purpose, second provides usage guidance. No filler.

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?

Given no output schema, description sufficiently explains purpose and behavior. Lacks error conditions but acceptable for simple save operation.

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%, baseline is 3. Description adds context for newPath (variant creation) but does not elaborate beyond schema for other parameters. Adequate but not exceptional.

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?

Description clearly states verb ('saves changes') and resource ('scene file'), and distinguishes from sibling tools by mentioning it's an alias and used for explicit saves or creating variants.

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?

Explicitly states when to use: 'for explicit saves or creating variants' and mentions that 'most scene modification tools save automatically', providing clear context and alternatives.

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