Skip to main content
Glama

script_source

DestructiveIdempotent

Read a script's full source or overwrite it entirely in Roblox Studio. Use it for whole-file reads and replacements; prefer patching or line edits for small changes to avoid resending the file.

Instructions

Read a script's full Source, or replace all of it. Reading is read-only; writing overwrites the whole script (open editor tabs update too) and is blocked in read-only mode. For small changes prefer patch_script (anchored find/replace) or edit_script_lines (a line range), which don't resend the file. To search across scripts use grep_scripts.

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

Input Schema

NameRequiredDescriptionDefault
pathYesScript, LocalScript or ModuleScript, e.g. "ServerScriptService.MusicService". 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.
sourceNoNew full Source. Omit to read the current Source instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / path / description
      Previous value: -"Full dotted instance path"New value: +"Script, LocalScript or ModuleScript, e.g. \"ServerScriptService.MusicService\". 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)\"."
    • changedInput schema / properties / source / description
      Previous value: -"omit to read; provide to overwrite the whole Source"New value: +"New full Source. Omit to read the current Source instead."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that writing overwrites the entire script, that open editor tabs are also updated, and that writes are blocked in read-only mode. The destructiveHint=true annotation is confirmed and given concrete operational meaning rather than merely restated.

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 sentences, each earning its place: the capability first, the write side-effects second, then disambiguation to siblings. No filler and no restatement of the title.

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 three-parameter tool with no output schema and full schema coverage, the description covers mode selection, mutation consequences, and alternatives. Nothing material is missing for correct invocation.

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%, so path, place, and source are already fully documented in the schema, including the "omit source to read" convention. The description adds the conceptual read-vs-write framing of the source parameter but no format or syntax detail beyond that, so the 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 with its dual mode exactly: "Read a script's full Source, or replace all of it." An agent immediately knows this is a whole-file read/write tool, distinct from the line- and patch-scoped siblings.

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?

Explicitly routes away from itself: "For small changes prefer patch_script (anchored find/replace) or edit_script_lines (a line range), which don't resend the file" and "To search across scripts use grep_scripts." Each named alternative comes with the condition that selects it.

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