Sets the main scene in a Godot project file while preserving other settings and comments. Use it to define which scene launches when the project runs.
Set the configured project main scene, preserving other settings and comments.
| Name | Required | Description | Default |
|---|---|---|---|
| scenePath | Yes | ||
| projectPath | Yes |
Changes observed during successful MCP inspections.
v0.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare a non-read-only, non-destructive, open-world mutation, so the bar is lower. The description adds real value by saying other settings and comments are preserved, but it omits that project.godot is being rewritten, whether the scene must exist beforehand, or what happens on an invalid path.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler, and the preservation clause is well placed. Nothing in it is redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no output schema and zero schema description coverage, the description should clarify path formats and side effects on project.godot. It only covers the preservation guarantee, leaving key invocation details to guesswork.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and there are two required parameters, yet the description never mentions projectPath or scenePath. It hints at a scenePath concept but leaves open whether it is a res:// path, absolute path, or scene name, and says nothing about what projectPath selects.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Set the configured project main scene"), which is a distinct operation from scene-editing siblings such as save_scene or modify_scene. It does not explicitly contrast itself with those siblings, but the resource is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the name and resource: an agent infers it is for changing which scene launches with the project. There is no statement of when to prefer it over save_scene/create_scene, nor any prerequisite such as requiring the scene to already exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.