Skip to main content
Glama
bebabinlarsson-blip

godot-omni

by bebabinlarsson-blip
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

node_manage

Manipulate Godot scene node trees: delete, duplicate, rename, reorder, reparent, group, transform nodes, and read children or group membership.

Instructions

Node tree manipulation (delete, duplicate, rename, reorder, reparent, groups, hierarchy reads).

Resource forms (prefer for active-session reads): godot://node/{path}/properties, godot://node/{path}/children, godot://node/{path}/groups

Ops: • get_children(path) Direct children of a node (name, type, path each). • get_groups(path) Group names the node belongs to. • delete(path, scene_file="") Remove the node. Cannot delete scene root. Undoable. • duplicate(path, name="", scene_file="") Deep-copy a node + children as a sibling. Cannot duplicate scene root. • rename(path, new_name, scene_file="") Rename a node. Sibling-name collision and "/" / ":" / "@" rules apply. • move(path, index, scene_file="") Reorder among siblings. Index 0 = first. • reparent(path, new_parent, scene_file="") Move under a new parent. Children preserved. Cannot move into descendants. • add_to_group(path, group, scene_file="") Add the node to a group. • remove_from_group(path, group, scene_file="") Remove the node from a group. • rotate(path, degrees, axis="y", relative=false, scene_file="") Rotate a 2D or 3D node by degrees. Undoable. • scale(path, scale, relative=false, scene_file="") Scale a 2D or 3D node or Control. Undoable. • translate(path, offset, relative=true, scene_file="") Move / offset a node position. Undoable. • call_method(path, method, args=[], scene_file="") Call any method on a node with arguments.

All write ops accept the optional scene_file guard — if non-empty, the mutation fails with EDITED_SCENE_MISMATCH when the editor's current scene doesn't match.

Canonical call shape: {"op": "<verb>", "params": {...}}. Flat op parameters are accepted as a compatibility alias when the client transmits them; op and session_id remain top-level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYes
paramsNo
session_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.28
    • changedInput schema / properties / op / enum
      Previous value: -[
-  "add_to_group",
-  "delete",
-  "duplicate",
-  "get_children",
-  "get_groups",
-  "instantiate_batch",
-  "move",
-  "remove_from_group",
-  "rename",
-  "reparent",
-  "rotate",
-  "scale",
-  "translate"
-]New value: +[
+  "add_to_group",
+  "call_method",
+  "delete",
+  "duplicate",
+  "get_children",
+  "get_groups",
+  "instantiate_batch",
+  "move",
+  "remove_from_group",
+  "rename",
+  "reparent",
+  "rotate",
+  "scale",
+  "translate"
+]
  2. Changed1 schema field changedv5.0.14
    • changedInput schema / properties / op / enum
      Previous value: -[
-  "add_to_group",
-  "delete",
-  "duplicate",
-  "get_children",
-  "get_groups",
-  "move",
-  "remove_from_group",
-  "rename",
-  "reparent",
-  "rotate",
-  "scale",
-  "translate"
-]New value: +[
+  "add_to_group",
+  "delete",
+  "duplicate",
+  "get_children",
+  "get_groups",
+  "instantiate_batch",
+  "move",
+  "remove_from_group",
+  "rename",
+  "reparent",
+  "rotate",
+  "scale",
+  "translate"
+]
  3. First observedv4.1.0

TDQS

A3.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses invariants like 'Cannot delete scene root', 'Cannot duplicate scene root', 'Cannot move into descendants', sibling-name collision rules, which operations are undoable, and the EDITED_SCENE_MISMATCH failure mode. It also warns that call_method can invoke 'any method', which is an important behavioral trait.

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?

The description is long but appropriately structured: a front-loaded summary, resource forms, compact bullet signatures, and a canonical call shape. There is minor redundancy between the resource-forms section and the get_children/get_groups ops, but the length is largely justified by the number of operations.

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?

The description is impressively complete for the documented ops, covering invariants, call shape, and scene_file guard behavior, and an output schema exists so return values need not be repeated. However, the operation enum includes instantiate_batch, which is entirely missing from the description, leaving a real gap in what an agent can validly invoke.

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?

The input schema has 0% description coverage and a generic params object, so the description compensates well by listing per-op parameters, defaults, and meanings such as 'Index 0 = first', 'axis="y"', and 'relative=false'. However, the enum includes instantiate_batch with no parameter documentation anywhere in the description, and the format of call_method's args is left underspecified.

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?

The description opens with a clear resource and action list: 'Node tree manipulation (delete, duplicate, rename, reorder, reparent, groups, hierarchy reads)' and then enumerates concrete operations. It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools like node_get_properties or node_create, and it omits the instantiate_batch op that appears in the input schema enum.

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?

There is some usage guidance, such as 'prefer for active-session reads' and the explanation of the scene_file guard and canonical call shape. However, the description does not state when to prefer this tool over alternatives or when not to use it, which is needed given the very large sibling list.

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