Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_script_get

Retrieve a Roblox script's source by instance path, optionally limited to a line range, to inspect or debug Luau code in Studio.

Instructions

Get script source, optionally a line range.

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": {
      "instance_path": "<instance_path>"
    },
    "name": "roblox_script_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
instance_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Get" implies a read, but it says nothing about permissions, behavior on non-script instances, truncation of large scripts, or what happens when start/end are omitted (default 0).

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?

A single front-loaded sentence with no filler, and the optional modifier is placed after the core action. It is efficient but borders on under-specification rather than tightness.

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?

An output schema exists, so return values need not be explained, and the tool is a simple three-parameter read. Still, with zero annotation and zero schema-description coverage, the description leaves the parameters and error behavior unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters. The phrase "line range" loosely maps to start/end but gives no basis (0- vs 1-indexed), no inclusivity rule, and no meaning for the default 0; instance_path is never mentioned at all.

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?

"Get script source" gives a specific verb and resource, and "optionally a line range" scopes the operation. It does not name or differentiate itself from siblings such as roblox_script_lines or roblox_script_edit, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives. The word "optionally" hints that the line range is a narrowing mode, but nothing tells the agent when to prefer roblox_script_lines or how this differs from roblox_read.

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