Skip to main content
Glama

copy_script_across

Destructive

Copy a script from one open Roblox Studio place to another, overwriting or creating the destination script and any missing folders. Use it to share modules between games.

Instructions

Copy one script's Source from one connected place into another, for example to share a module between two games. Both places must be open in Studio. The destination script is overwritten if it exists, or created with any missing folders if it doesn't. Use list_places to get the place names or ids.

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": {
      "fromPlace": "<fromPlace>",
      "sourcePath": "<sourcePath>",
      "toPlace": "<toPlace>"
    },
    "name": "copy_script_across"
  }
}

Input Schema

NameRequiredDescriptionDefault
toPlaceYesPlace to copy into: its PlaceId or name, as list_places shows.
destPathNoDot path for the script in the destination place. Defaults to the same path as sourcePath.
fromPlaceYesPlace to copy from: its PlaceId or name, as list_places shows.
sourcePathYesDot path of the script in the source place, e.g. "ReplicatedStorage.Shared.Util".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • changedInput schema / properties / destPath / description
      Previous value: -"Destination script path (defaults to sourcePath)"New value: +"Dot path for the script in the destination place. Defaults to the same path as sourcePath."
    • changedInput schema / properties / fromPlace / description
      Previous value: -"Source place (PlaceId or name)"New value: +"Place to copy from: its PlaceId or name, as list_places shows."
    • changedInput schema / properties / sourcePath / description
      Previous value: -"Script path in the source place"New value: +"Dot path of the script in the source place, e.g. \"ReplicatedStorage.Shared.Util\"."
    • changedInput schema / properties / toPlace / description
      Previous value: -"Destination place (PlaceId or name)"New value: +"Place to copy into: its PlaceId or name, as list_places shows."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description specifies the exact destructive effect: an existing destination script is overwritten, and missing folders are created when the destination path does not exist. It also discloses the Studio-open prerequisite, which is important operational context for a cross-place copy.

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?

The description is four short sentences, front-loaded with the primary action and followed by prerequisites, side effects, and a helper tool reference. Every sentence contributes useful information without repetition.

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

Completeness5/5

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

For a destructive cross-place copy with full schema coverage and annotations covering safety, the description supplies the key operational details an agent needs: scope, Studio prerequisite, overwrite behavior, folder creation, and list_places usage. No output schema is present, but the definition is complete enough to call the tool correctly.

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%, so the schema already documents all four parameters, including the destPath default. The description adds only the list_places hint for place identifiers and does not add further meaning beyond the schema.

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?

The description states a specific verb and resource: copying one script's Source from one connected place into another. It adds a concrete use case, sharing a module between two games, which makes the operation distinct from editing or creating scripts.

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?

It gives a clear prerequisite that both places must be open in Studio and points the agent to list_places for valid place names or ids. It does not explicitly state when not to use this tool or name a direct alternative, so it stops short of full when/when-not guidance.

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