Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_script_set

Set a Roblox script's source code with a dry-run preview by default, letting you validate changes before applying them.

Instructions

Set script source. Dry-run by default.

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

Input Schema

NameRequiredDescriptionDefault
sourceYes
dry_runNo
instance_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the entire behavioral burden. It discloses only that dry-run is the default, which merely restates the schema's default:true, and says nothing about whether the write overwrites the whole source, whether it requires an active Studio session, or what a dry run actually returns.

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?

Two short sentences, front-loaded with the operation and immediately followed by the most consequential behavioral note. There is no filler, though the terseness edges into under-specification rather than genuine economy.

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

Completeness2/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. For a mutation tool with zero annotations and zero documented parameters, however, the description omits the essential context an agent needs to invoke it safely and correctly.

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%, so the description must compensate and it does not. instance_path format and source semantics (full replacement vs. fragment) are left entirely undefined, and dry_run is only echoed from the schema default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Set script source" gives a verb and a resource, so the basic operation is identifiable. But it does not distinguish full-source replacement from the incremental changes implied by siblings like roblox_script_edit and roblox_replace, so an agent cannot tell which one to pick from the text alone.

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?

The only usage-relevant statement is "Dry-run by default," which hints at a preview-then-apply workflow but never states when to use this rather than script_edit or replace, nor what conditions require dry_run=false. No alternatives or exclusions are named.

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