Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_script_lines

Insert Luau code after a specified line or delete a line range in a Roblox script, enabling precise edits without rewriting the whole script.

Instructions

Insert (after start_line) or delete (start_line..end_line) script lines.

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_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoinsert
contentNo
end_lineNo
start_lineNo
instance_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose the two operating modes plus their positional semantics (insert positioned after start_line, delete covering start_line..end_line). It omits permissions/auth needs, whether deletion is recoverable, what happens to defaults of 0, and whether content is mandatory for insert — significant 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the two modes are presented before their parameters. The parenthetical notation is compact but slightly cryptic, keeping it from a 5.

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?

Five parameters at 0% schema coverage, no annotations, and a mutation surface — the description should explain instance_path, valid action values, and default-line behavior. An output schema exists, so return values need not be described, but the input side is badly under-specified for a destructive editing tool.

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 only partially does: it explains start_line/end_line semantics but never mentions instance_path, which is the only required parameter. The action parameter has no enum in the schema and the description never maps the words 'insert'/'delete' to action values, and the meaning of content is left implicit.

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?

States specific verbs (insert/delete) against a specific resource (script lines), so the agent knows this mutates script content rather than reading it. It does not explicitly differentiate from sibling editors like roblox_script_edit or roblox_script_set, so it stops short of a 5.

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?

No when-to-use guidance: nothing says when to pick this over roblox_script_edit, roblox_script_set, or roblox_replace, and no prerequisites or ordering constraints are stated. The implied usage can be inferred from the two modes, but nothing is explicit.

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