2021 Roblox Studio MCP Bridge

Overview Schema Source Related Servers Discussions Admin

read_script

Fetches the complete source code of a Roblox Studio script using its path, so AI assistants can inspect scripts for editing or debugging.

Instructions

Reads the complete Source text of a Script

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": {
      "path": "<path>"
    },
    "name": "read_script"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.5.6Sep 30, 2026
- removedInput schema / properties / path / description
```
Removed value: -"Full instance path (e.g. 'game.ServerScriptService.MyScript')"
```
First observedv1.0.0Sep 12, 2026

TDQS

C2.7/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 full behavioral burden. It implies a read-only operation and that the full (untruncated) source is returned, but says nothing about permissions, behavior on missing/invalid paths, size limits, or side effects.

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 short, front-loaded sentence with no filler. It is efficient, though its brevity contributes to the documentation gaps noted elsewhere rather than being a flaw of structure itself.

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?

For a tool with no annotations, no output schema, an undocumented parameter, and a confusingly similar sibling, the description is too thin. An agent lacks enough context on routing, path semantics, and return behavior to invoke it confidently.

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?

The single 'path' parameter has 0% schema description coverage, and the description does not compensate by explaining what the path is relative to, its format, or examples. The parameter name is intuitive but effectively undocumented.

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 ('Reads the complete Source text of a Script') and signals scope with 'complete'. However, it makes no attempt to distinguish itself from the near-identically named sibling 'script_read', leaving the agent unable to tell the two apart without opening schemas.

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?

There is no statement of when to use this tool, when not to, or which alternative to prefer. With siblings like script_read and script_grep that plausibly overlap, the absence of any routing guidance is a real gap.

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