Skip to main content
Glama
sansaks-jpg

Gamedev All-in-One MCP

by sansaks-jpg

Roblox Edit Script Lines

roblox_edit_script_lines

Replace a substring in a Roblox script's source by specifying the exact old text and new text to perform a search-and-replace operation.

Instructions

Replace a substring in a script's source using old_string/new_string matching, similar to search-and-replace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFull instance path of the script.
oldStringYesExact text to find in the script source.
newStringYesReplacement text.
waitForResponseMsNoHow long to wait for a runtime response.
Behavior2/5

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

No annotations are provided. The description does not disclose if the replacement is in-place, requires authentication, affects all occurrences, or behavior when old_string is not found. This lack of detail is insufficient 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 sentence of 14 words, front-loaded with the action (Replace a substring), and contains no wasted words. It is highly concise.

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?

No output schema exists, and the description does not mention return values, success indicators, or constraints like working on running scripts. For a tool that modifies script source, more behavioral context is needed.

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 baseline is 3. The description adds 'similar to search-and-replace', clarifying the operation type but not adding significant meaning beyond the schema's parameter descriptions.

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 action: replace a substring in a script's source using old_string/new_string matching, similar to search-and-replace. It distinguishes from sibling tools like roblox_set_script_source (full replacement) and roblox_grep_scripts (search).

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

Usage Guidelines3/5

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

The description says 'similar to search-and-replace', which implies usage for replacing specific text. However, it does not explicitly state when not to use it or suggest alternatives like roblox_set_script_source for full replacement.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sansaks-jpg/gamedev-all-in-one-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server