Skip to main content
Glama

studio_sync_native

Sync native .rp edits back into the original Studio source document in preview or apply mode, mapping nodes, component overrides, and conflicts to author targets.

Instructions

将原生 .rp 修改自动收敛回同一 Studio 源文档(preview/apply)。通过基线符号与 GUID 映射到真实作者源 target/propertyMap/父内容盒坐标,覆盖普通节点、宏参数、组件实例覆盖、流式布局排布提示、非激活面板状态、中继器模板(默认保护 =item.xxx 公式不被首行字面量覆盖)与多页三方冲突裁决。

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": {
      "rpPath": "<rpPath>"
    },
    "name": "studio_sync_native"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
modeNo
portNo
asyncNotrue在工程内持久记录并返回句柄;结果未知时按requestKey核对,不重做
preferNo
rpPathYes
outRpPathNo
rebuildRpNo
baseRpPathNo
projectDirNo
requestKeyNo
previewHashNo
resolutionsNo
baseRevisionNo
baselinePathNo
idempotencyKeyNo
allowFormulaOverwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds real behavioral context beyond them: the default guard that protects '=item.xxx' repeater formulas from being overwritten by first-row literals, plus multi-page three-way conflict adjudication. It does not state overwrite risk for other properties or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single run-on sentence that piles a feature checklist (nodes, macro params, instance overrides, layout hints, inactive panels, repeater templates, conflict resolution) after the purpose clause. Length is contained, but the jargon pile-up buries the actionable information and is not front-loaded by task.

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?

This is a high-complexity sync tool with 17 parameters, no output schema, and near-zero schema description coverage. The description explains what it does conceptually but says nothing about how to supply the many optional path/key/mode parameters or what a caller gets back, so it is not complete for the tool's complexity.

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?

With 17 parameters and 6% schema description coverage, the description must carry parameter meaning, but it only loosely gestures at mode (preview/apply), baseline inputs (baseline symbols/GUID), and formula overwrite behavior. outRpPath, rebuildRp, prefer, resolutions, requestKey, idempotencyKey, projectDir and baseRevision are left unexplained in both schema and description.

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 opening clause '将原生 .rp 修改自动收敛回同一 Studio 源文档(preview/apply)' names a specific action (converging native .rp edits back to the Studio source document) and a specific resource. It is not differentiated against close siblings like studio_merge_document or studio_apply_commands, but the core purpose is legible.

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?

The only usage hint is the parenthetical '(preview/apply)', which implies a dry-run-then-apply workflow but never states it. There is no when-to-use/when-not guidance, no prerequisites, and no exclusion relative to the merge/apply siblings.

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