Skip to main content
Glama

save_scene

Save modifications to a Godot scene file, optionally creating variants by specifying a new path.

Instructions

Save changes to a scene file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to the Godot project directory
scenePathYesPath to the scene file (relative to project)
newPathNoOptional: New path to save the scene to (for creating variants)

Implementation Reference

  • The main handler function for the 'save_scene' tool. It validates the input parameters (projectPath, scenePath, optional newPath), checks project and scene validity, prepares parameters, executes the underlying Godot 'save_scene' operation via executeOperation, handles errors, and returns success or error response.
    private async handleSaveScene(args: any) {
      // Normalize parameters to camelCase
      args = this.normalizeParameters(args);
      
      if (!args.projectPath || !args.scenePath) {
        return this.createErrorResponse(
          'Missing required parameters',
          ['Provide projectPath and scenePath']
        );
      }
    
      if (!this.validatePath(args.projectPath) || !this.validatePath(args.scenePath)) {
        return this.createErrorResponse(
          'Invalid path',
          ['Provide valid paths without ".." or other potentially unsafe characters']
        );
      }
    
      // If newPath is provided, validate it
      if (args.newPath && !this.validatePath(args.newPath)) {
        return this.createErrorResponse(
          'Invalid new path',
          ['Provide a valid new path without ".." or other potentially unsafe characters']
        );
      }
    
      try {
        // Check if the project directory exists and contains a project.godot file
        const projectFile = join(args.projectPath, 'project.godot');
        if (!existsSync(projectFile)) {
          return this.createErrorResponse(
            `Not a valid Godot project: ${args.projectPath}`,
            [
              'Ensure the path points to a directory containing a project.godot file',
              'Use list_projects to find valid Godot projects',
            ]
          );
        }
    
        // Check if the scene file exists
        const scenePath = join(args.projectPath, args.scenePath);
        if (!existsSync(scenePath)) {
          return this.createErrorResponse(
            `Scene file does not exist: ${args.scenePath}`,
            [
              'Ensure the scene path is correct',
              'Use create_scene to create a new scene first',
            ]
          );
        }
    
        // Prepare parameters for the operation (already in camelCase)
        const params: any = {
          scenePath: args.scenePath,
        };
    
        // Add optional parameters
        if (args.newPath) {
          params.newPath = args.newPath;
        }
    
        // Execute the operation
        const { stdout, stderr } = await this.executeOperation('save_scene', params, args.projectPath);
    
        if (stderr && stderr.includes('Failed to')) {
          return this.createErrorResponse(
            `Failed to save scene: ${stderr}`,
            [
              'Check if the scene file is valid',
              'Ensure you have write permissions to the output path',
              'Verify the scene can be properly packed',
            ]
          );
        }
    
        const savePath = args.newPath || args.scenePath;
        return {
          content: [
            {
              type: 'text',
              text: `Scene saved successfully to: ${savePath}\n\nOutput: ${stdout}`,
            },
          ],
        };
      } catch (error: any) {
        return this.createErrorResponse(
          `Failed to save scene: ${error?.message || 'Unknown error'}`,
          [
            'Ensure Godot is installed correctly',
            'Check if the GODOT_PATH environment variable is set correctly',
            'Verify the project path is accessible',
          ]
        );
      }
    }
  • Defines the input schema and metadata for the 'save_scene' tool in the ListTools response, specifying required parameters projectPath and scenePath, and optional newPath.
      description: 'Save changes to a scene file',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description: 'Path to the Godot project directory',
          },
          scenePath: {
            type: 'string',
            description: 'Path to the scene file (relative to project)',
          },
          newPath: {
            type: 'string',
            description: 'Optional: New path to save the scene to (for creating variants)',
          },
        },
        required: ['projectPath', 'scenePath'],
      },
    },
  • src/index.ts:956-957 (registration)
    Registers the 'save_scene' tool handler in the switch statement for CallToolRequestSchema, dispatching to handleSaveScene.
    case 'save_scene':
      return await this.handleSaveScene(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the tool saves changes, implying mutation, but doesn't disclose critical traits like permission requirements, whether it overwrites existing files, error handling, or side effects. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with zero waste—every word contributes directly to the purpose. It's front-loaded and appropriately sized for the tool's complexity, avoiding unnecessary elaboration while remaining clear. This exemplifies ideal conciseness for a straightforward tool.

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

Completeness2/5

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

Given the tool's mutation nature, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'changes' are, how they're applied, what happens on success/failure, or return values. For a 3-parameter tool that modifies files, more context is needed to guide an agent effectively, especially with no structured safety or output information.

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 description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond implying 'newPath' is for creating variants, which is already covered in the schema's description. This meets the baseline of 3, as the schema handles parameter semantics adequately without extra value from the description.

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?

The description clearly states the action ('Save changes') and resource ('to a scene file'), making the purpose immediately understandable. It distinguishes from siblings like 'create_scene' (new creation) and 'update_project_uids' (different resource), though it doesn't explicitly contrast with them. The verb+resource combination is specific but could be more detailed about what 'changes' entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create_scene' or 'update_project_uids'. It doesn't mention prerequisites (e.g., needing an existing scene), exclusions, or contextual triggers. Usage is implied from the action but not explicitly defined, leaving gaps for an agent to infer correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zycroft/godot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server