Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_replace

Find and replace text across Roblox scripts with a dry-run preview by default, so you can review changes before applying them.

Instructions

Find and replace across scripts. 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": {
      "pattern": "<pattern>",
      "replacement": "<replacement>"
    },
    "name": "roblox_replace"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
patternYes
replacementYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing that this is a mutation. It only notes the dry-run default (which already appears as schema default=true) and omits the blast radius (which scripts are scanned - whole place, open scripts, selection?), whether the operation is reversible, and any permission or rate considerations.

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 action, with no filler. The second sentence partly restates the schema default, which is the only wasted clause, but overall it is tight and scannable.

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?

The existence of an output schema means return values need no explanation, but for a bulk mutation tool over an entire codebase the description is thin: scope of the replacement, pattern semantics, and failure/rollback behavior are all left to guesswork.

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 define the three parameters, but it only echoes dry_run. Critically, "pattern" is ambiguous - regex versus literal string, and case sensitivity - and "replacement" semantics (capture groups, empty string) are unaddressed.

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?

"Find and replace across scripts" names a specific verb pair and resource, and the scope word "across scripts" separates it from a single-script editor like roblox_script_edit or a pure search like roblox_grep. No sibling is named explicitly, so differentiation is by implication only.

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?

"Dry-run by default" implies a preview-then-apply workflow, which is actionable guidance. However, it never says when to prefer this over roblox_grep (find) or roblox_script_edit (targeted edits), nor does it state prerequisites such as needing scripts open or a selection.

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