Skip to main content
Glama
AnkleBreaker-Studio

Unity MCP Server

by AnkleBreaker-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unity_scene_save

Save the current Unity scene to persist changes. For never-saved scenes, provide a path to avoid Unity's interactive Save dialog.

Instructions

Save the current scene. A never-saved scene requires path, else Unity opens its interactive Save dialog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoSave-As asset path, e.g. 'Assets/Scenes/MyScene.unity'.
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
overwriteNoReplace another existing scene at path (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.36.0
    • addedInput schema / properties / overwrite
      Added value: +{
+  "description": "Replace another existing scene at path (default false)",
+  "type": "boolean"
+}
    • changedInput schema / properties / path / description
      Previous value: -"Asset path to save to, e.g. 'Assets/Scenes/MyScene.unity'. Required for a scene that has never been saved; also acts as Save-As."New value: +"Save-As asset path, e.g. 'Assets/Scenes/MyScene.unity'."
  2. Changed2 schema fields changedv2.35.6
    • addedInput schema / properties / path
      Added value: +{
+  "description": "Asset path to save to, e.g. 'Assets/Scenes/MyScene.unity'. Required for a scene that has never been saved; also acts as Save-As.",
+  "type": "string"
+}
    • changedInput schema / properties / port / description
      Previous value: -"Target Unity instance port for parallel-safe routing. Get this from unity_select_instance. When working with multiple Unity instances, ALWAYS include this parameter."New value: +"Unity instance port (from unity_select_instance). Always include it when multiple instances run."
  3. Addedv2.28.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses that omitting path on an unsaved scene triggers an interactive Unity dialog — a real side effect an agent must avoid — but says nothing about permissions, the multi-instance targeting requirement, or what a successful save returns.

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 short sentences, front-loaded with the core action and followed immediately by the one non-obvious edge case. No filler or redundancy.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the essential behavior and the path edge case, but omits the port/multi-instance caveat (deferred entirely to the schema) and any failure or return-value context.

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 all three parameters are already documented in the schema, establishing the baseline of 3. The description adds the conditional semantics of `path` (required only for never-saved scenes), which is a useful nuance beyond the schema's field-level docs.

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 precise verb+resource ('Save the current scene'), which clearly distinguishes it from sibling tools like unity_scene_open, unity_scene_new, and unity_asset_create_prefab. It stops short of explicitly noting that this is the only scene-save tool, but the resource scope is unambiguous.

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

Usage Guidelines4/5

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

Gives a concrete condition: a never-saved scene requires `path`, otherwise Unity falls back to an interactive Save dialog. This tells the agent when path matters, though it offers no exclusions or comparison to any alternative tool (none closely competes here).

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