Skip to main content
Glama

rename_instance

DestructiveIdempotent

Rename a Roblox instance by dot path and return its new path as one Studio undo step. Use it to update object names in the DataModel, and check scripts with grep first.

Instructions

Change an instance's Name and return its new path. Recorded as one Studio undo step. Scripts that find the instance by its old name will stop finding it, so search with grep_scripts first when renaming something code refers to.

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>",
      "newName": "<newName>"
    },
    "name": "rename_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesInstance to rename. 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.
newNameYesThe new Name. Duplicate names are allowed; Tufan then addresses the later sibling as "Name (2)".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / newName / description
      Added value: +"The new Name. Duplicate names are allowed; Tufan then addresses the later sibling as \"Name (2)\"."
    • addedInput schema / properties / path / description
      Added value: +"Instance to rename. 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.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely new context the annotations cannot convey: the change is recorded as one Studio undo step (i.e., reversible in-editor), and downstream name-based lookups break after the rename. It stops short of describing multi-place behavior or failure modes.

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?

Three short sentences, front-loaded with the action and result, then the undo guarantee, then the caveat. No restatement of the name or title and no filler.

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 three-parameter mutation with no output schema, the description covers outcome (new path), reversibility (single undo step), and the main hazard (broken name-based references). What remains, such as multi-place selection behavior, is handled by the schema's place parameter description.

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 coverage is 100% and each parameter is already well documented, including dot-path syntax and duplicate-name suffixing. The description mentions the new path is returned but adds no naming constraints, format rules, or meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Change an instance's Name") plus the observable result ("return its new path"), which cleanly separates it from create_instance, move_instance, and delete_instance. An agent can identify this as the rename operation without opening the schema.

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 precondition and names the sibling to use first: "search with grep_scripts first when renaming something code refers to." That is real when-to guidance, though it covers a code-safety caveat rather than distinguishing rename from other mutation paths more broadly.

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