Skip to main content
Glama

sync_push

Send locally edited or new script files to Roblox Studio, refusing conflicting overwrites unless forced; optionally create new scripts and delete Studio files missing locally.

Instructions

Send locally edited/new script files to Studio. Refuses to overwrite scripts that were also changed in Studio since the last sync (conflict) unless force. New files are created (class from suffix, optional --!runcontext client|server). Deleted files are only deleted in Studio with delete_missing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNo
filesNoOnly these files (relative to dir).
forceNo
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.
dry_runNoOnly list what would be pushed.
sourcemapNoUpdate sourcemap.json after pushing.
delete_missingNoDelete in Studio the scripts whose files were deleted locally.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the conflict-refusal rule behind force, that new files get a class derived from the suffix, that deleted files are NOT removed from Studio unless delete_missing is set, and the optional runcontext header. It omits what a push returns and whether partial failures roll back, but the destructive behaviors are all surfaced.

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?

Three tight sentences, front-loaded with the core action, then escalating to conflict handling and deletion. Every clause carries behavioral information; the runcontext parenthetical is dense but earns its place as otherwise-undocumented syntax.

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

Completeness4/5

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

For a 7-parameter mutation tool with no annotations and no output schema, the description covers the high-risk behaviors (conflict, overwrite, deletion) that an agent most needs. The main residual gap is that, absent an output schema, the agent learns nothing about what a push returns or how failures are reported.

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

Parameters4/5

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

Schema coverage is 71%, and the description adds genuine meaning beyond the schema: it explains force as the override for the conflict rule (the schema only names the boolean) and clarifies that delete_missing controls real deletion in Studio. It also documents the `--!runcontext client|server` file convention, which appears nowhere in the schema. dir's default and sourcemap/dry_run semantics are left to the schema.

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?

"Send locally edited/new script files to Studio" gives a specific verb (send/push), resource (script files), and direction (local → Studio), which implicitly separates it from sync_pull. It never names an alternative explicitly, but the directionality makes the tool's role unambiguous.

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 conveys important conditions of use — overwrite is refused on conflict unless force, deletion requires delete_missing — which implies when the tool applies. However, it never states when to prefer sync_push vs sync_pull or sync_watch, nor any prerequisites (e.g., a Studio must be attached, a prior sync status check).

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