Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

save_scene

Save the current Godot scene to disk, preserving modifications and ensuring AI-assisted edits are stored in your game project.

Instructions

Save current scene. (Compatibility tool)

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
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description carries full burden but reveals almost nothing about side effects, return values, or the meaning of 'Compatibility tool'. Fails to explain why a save operation has timeoutMs and autoConnect parameters, which suggests non-standard behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief (4 words plus parenthetical), but the '(Compatibility tool)' remark wastes space without clarifying scope or deprecation status. Front-loaded but underspecified.

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?

Insufficient for a filesystem-mutating tool with no annotations, no output schema, and undocumented parameters. Missing: error conditions, overwrite behavior, and what 'compatibility' implies for the save format.

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

Parameters1/5

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

Schema has 0% description coverage for timeoutMs and autoConnect. Description compensates with zero information, leaving critical parameters undocumented. The additionalProperties: true flag is also not mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the basic action (save) and target (current scene), but 'current' is ambiguous (editor context vs runtime), and the '(Compatibility tool)' parenthetical introduces confusion without explanation. Does not distinguish from export_project or how it differs from implicit saving in other tools.

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

Usage Guidelines1/5

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

Provides no guidance on when to use this versus export_project, create_scene, or open_scene. No mention of prerequisites (e.g., unsaved changes) or when saving is prohibited.

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