Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_node_owner

Set a node’s owner to enable saving packed scenes by specifying the target node path and owner node path.

Instructions

Set the owner of a node (required for saving packed scenes).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_path": "<node_path>",
      "owner_path": "<owner_path>"
    },
    "name": "set_node_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath of the node
owner_pathYesPath of the owner node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals that this setting is a precondition for packing scenes, but says nothing about whether an existing owner is replaced, whether the node must already exist, or what happens on an invalid owner_path.

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?

One short sentence with the purpose front-loaded and the rationale in parentheses; nothing is redundant or padded.

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

Completeness4/5

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

For a two-parameter tool with fully described inputs and no output schema, the definition covers what it does and why it matters. The remaining gaps—replacement behavior and error conditions—are modest but real for an unannotated mutation tool.

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

Parameters4/5

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

Schema coverage is 100% with clear per-parameter descriptions, so the baseline is a 3. The description adds meaning by framing node_path and owner_path as a relationship (a node and its owning node) tied to scene-saving semantics, slightly exceeding the schema alone.

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 and resource ('Set the owner of a node'), which is clearly distinct from the many other set_* siblings operating on properties, materials, or settings. The parenthetical adds the domain consequence, though it doesn't explicitly contrast with alternatives.

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?

The note 'required for saving packed scenes' implicitly tells the agent when this matters, which is genuine context. However, it gives no explicit when-to-use rule, no prerequisites (e.g., that the owner path must already exist or be an ancestor), and no guidance versus related tools like move_node or add_node.

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