Skip to main content
Glama

move_instance

DestructiveIdempotent

Move an instance and all its descendants under a new parent, returning the updated path as a single undoable Studio step. Use it to reorganize hierarchies without copying or renaming them.

Instructions

Move an instance (with its descendants) under a different parent and return its new path. Recorded as one Studio undo step. To change only the name use rename_instance; to keep the original and place a copy, use clone_instance.

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": {
      "path": "<path>",
      "newParentPath": "<newParentPath>"
    },
    "name": "move_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesInstance to move. Dot path from the DataModel root, e.g. "Workspace.Map.Door" or "StarterGui.HUD.Frame". A leading "game." is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. "Part (2)".
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
newParentPathYesNew parent. Dot path from the DataModel root, e.g. "Workspace.Map.Door" or "StarterGui.HUD.Frame". A leading "game." is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. "Part (2)".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / newParentPath / description
      Added value: +"New parent. Dot path from the DataModel root, e.g. \"Workspace.Map.Door\" or \"StarterGui.HUD.Frame\". A leading \"game.\" is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. \"Part (2)\"."
    • addedInput schema / properties / path / description
      Added value: +"Instance to move. Dot path from the DataModel root, e.g. \"Workspace.Map.Door\" or \"StarterGui.HUD.Frame\". A leading \"game.\" is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. \"Part (2)\"."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag this as a destructive, idempotent write; the description adds real value beyond them by disclosing that descendants move with the instance, that the new path is returned, and that the whole operation collapses into a single Studio undo step. What's missing is failure behavior (e.g., circular parenting, cross-place moves when `place` differs).

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 tight sentences: the action and its subtree/return/undo consequences come first, then the disambiguation clause. No filler and nothing repeated from the schema.

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?

With three well-documented parameters, an explicit return statement, and annotations covering the safety profile, an agent has what it needs to call this. Only edge-case behavior on invalid targets or the optional `place` scoping is unaddressed.

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%, including the dot-path format and duplicate-suffix conventions, so the schema carries parameter meaning. The description adds nothing about the optional `place` parameter's binding semantics, leaving it at the baseline.

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

Purpose5/5

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

"Move an instance (with its descendants) under a different parent and return its new path" gives a specific verb, resource, and scope, and explicitly contrasts itself with rename_instance and clone_instance so the agent can pick correctly without opening schemas.

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

Usage Guidelines5/5

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

It names two concrete alternative siblings and the exact condition that selects each (name change vs. copy). The only thing left implicit is that a parent cannot be moved into its own descendant, but the alternatives routing is fully explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.