Skip to main content
Glama
Sign In
Roblox Studio MCP Server

Roblox Studio MCP Server

by boshyxd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_script_source

Update script source code safely in Roblox Studio without using loadstring. Input the script instance path and the new source code to modify scripts directly in the Studio environment.

Instructions

Safely set the source code of a script object without using loadstring (Studio only)

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": {
      "instancePath": "<instancePath>",
      "source": "<source>"
    },
    "name": "set_script_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
instancePathYesPath to the script instance (e.g., "game.ServerScriptService.MainScript")
sourceYesNew source code for the script

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context about safety ('safely') and platform restriction ('Studio only'), but does not cover other critical behaviors such as error handling, permission requirements, or whether the change is reversible. This leaves gaps for a mutation tool.

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 a single, efficient sentence that front-loads the key action ('Safely set the source code') and includes essential constraints without unnecessary words. Every part earns its place by clarifying purpose and usage context concisely.

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?

Given a mutation tool with no annotations and no output schema, the description is moderately complete. It covers purpose and key constraints but lacks details on behavioral aspects like error responses, side effects, or return values. For a tool that modifies script source, more context on safety implications or success indicators would be beneficial.

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 fully documents both parameters ('instancePath' and 'source'). The description does not add any parameter-specific details beyond what the schema provides, such as syntax examples or constraints on source code format. Baseline 3 is appropriate when the schema handles all parameter documentation.

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 clearly states the specific action ('set the source code'), target resource ('of a script object'), and key constraints ('without using loadstring', 'Studio only'). It precisely distinguishes this from sibling tools like 'set_property' or 'get_script_source' by focusing on script source modification with safety and platform limitations.

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?

The description provides clear context for usage ('Studio only') and a key constraint ('without using loadstring'), which implicitly guides when to use this tool. However, it does not explicitly state when to use alternatives like 'set_property' for other properties or 'get_script_source' for reading, nor does it mention prerequisites like script existence or permissions.

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

Deploy Server

Other Tools

Related Tools