Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

save_scene

Save the currently open Godot scene to disk, or specify an optional res:// path to save it as a new scene file.

Instructions

Save the currently open scene.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional res:// path to save as (save-as)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it discloses nothing about the write: whether an existing file is overwritten, whether the res:// path must already exist, what happens when no scene is open, or whether errors are raised. "Save" alone signals mutation but gives no operational context.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity trades away information an agent might want about the optional path argument.

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

Completeness3/5

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

For a one-parameter, no-annotation tool that writes to disk, the definition is minimally viable but missing the write semantics (overwrite behavior, prerequisite of an open scene, failure modes) that would make it reliably callable.

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% and the schema already explains the path parameter in detail (optional res:// path, save-as semantics). The description adds no meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb plus resource ("Save the currently open scene"), which lets an agent distinguish it from open_scene/close_scene/create_scene in the sibling list. It stops short of naming the closest alternative behavior (save-as), which is only implied by the parameter.

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

Usage Guidelines3/5

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

Usage is only implied: it acts on whatever scene is currently open, so an agent can infer a scene must first be opened via open_scene. There is no explicit statement of when to omit the path versus provide one, nor any exclusion or alternative route.

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

Deploy Server

Other Tools