Skip to main content
Glama
Sign In
2021 Roblox Studio MCP Bridge

2021 Roblox Studio MCP Bridge

by aswdffdas-sudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

multi_edit

Edits or creates scripts in Roblox Studio via multiple file changes, letting AI assistants modify Luau code in the DataModel.

Instructions

Edits or creates scripts in Studio

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": {
      "file_path": "<file_path>",
      "edits": "<edits>"
    },
    "name": "multi_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
editsYes
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.6

TDQS

C2.4/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden. It says 'Edits or creates' but does not disclose whether edits are atomic, whether creating overwrites existing files, what permissions are required, or what side effects occur.

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 sentence with no wasted words, front-loading the core action. However, it is terse for a mutation tool whose parameters are entirely undocumented, making the brevity partly under-specification rather than efficient conciseness.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, no output schema, and 0% parameter documentation, the description is far too thin. It does not explain multi-edit behavior, create vs. overwrite semantics, or any prerequisite, leaving the agent unable to invoke it correctly without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters. The description adds no meaning about file_path (path format? relative/absolute?) or edits (array element shape? edit operation types?). It leaves the agent with no parameter guidance.

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 a specific verb and resource: 'Edits or creates scripts in Studio.' An agent can tell it is a mutation tool for scripts, but it does not distinguish from the sibling write_script tool or clarify the 'multi' aspect of multi_edit.

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 guidance on when to use this tool versus alternatives like write_script or create_instance. The description only states what it does, not the context or conditions that select it.

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