Skip to main content
Glama

sync_watch

Keep local files and Roblox Studio in live two-way sync: push saved local changes to Studio and pull Studio edits at set intervals, with an initial pull for unsynced folders.

Instructions

Live two-way sync: local file saves are pushed to Studio automatically, and edits made in Studio are pulled every few seconds. Pulls first if the folder is not synced yet.

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": {
      "on": "<on>"
    },
    "name": "sync_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes
dirNo
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.
sourcemapNoUpdate sourcemap.json on pull/push.
interval_sNoStudio polling interval. Default 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses automatic push on local saves, periodic pulls from Studio, and an initial pull when the folder is not yet synced. It still omits what turning the watcher off does, conflict handling, and error behavior.

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 two tightly written sentences, front-loads the core two-way sync behavior, and wastes no words. The initial-pull caveat is placed efficiently after the main behavior.

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 definition covers the central live-sync behavior, but for a five-parameter tool with no annotations and no output schema, it leaves meaningful gaps around the required on flag, default folder behavior, stopping the watcher, and what the tool returns.

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 coverage is 60%, with descriptions for studio, sourcemap, and interval_s but not for the required on flag or dir. The description indirectly adds meaning about periodic Studio polling and unsynced-folder behavior, but it does not clarify the required on toggle or folder parameter.

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?

The description states a specific resource and behavior: live two-way sync between local files and Studio, with automatic pushes and periodic pulls. It is clear enough to distinguish this from one-shot sync operations, though it does not explicitly name sibling tools such as sync_pull or sync_push.

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?

Usage is implied by the phrase 'Live two-way sync,' making it clear this is for continuous synchronization rather than a one-time pull or push. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives.

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