Skip to main content
Glama

studio_merge_document

Merge concurrent human/AI edits or external JSON/RP1 files via three-way structured merge: auto-combine unrelated changes and report field, layout, instance, and reference conflicts for preview/apply.

Instructions

对同一工程执行人类/AI并发编辑或外部 JSON/RP1 文件的三方结构化合并(preview/apply/check-external)。自动合并无关修改,显式报出同字段、删改、跨容器重挂、布局耦合(如 x vs right、父流式 vs 子坐标)、组件实例覆盖与引用冲突,支持逐项裁决并写入单步可撤销事务。

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": "studio_merge_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
modeNo
portNo
actorNo
labelNo
preferNo
baseDocNo
oursDocNo
verboseNo
clientIdNo
maxBytesNo
theirsDocNo
theirsRp1No
includeDocNo
projectDirNo
previewHashNo
resolutionsNo
baseRevisionNo
includeSceneNo
theirsPageIdNo
baseVersionIdNo
idempotencyKeyNo
theirsCommandsNo
theirsParentIdNo
theirsSourceModeNo
externalSourcePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.3/5.0
Behavior4/5

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

Beyond annotations, the description discloses that unrelated changes are auto-merged, conflict categories are explicitly reported, item-by-item resolution is supported, and writes occur in a single-step undoable transaction. This is strong behavioral context and is consistent with readOnlyHint=false and destructiveHint=false, though it does not cover auth, rate limits, or 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.

Conciseness4/5

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

The description is a single, front-loaded sentence that packs in purpose, modes, conflict types, and transaction behavior without filler. It is dense but appropriately sized for a complex merge tool, though a slightly more structured format could improve scanability.

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 26-parameter tool with no output schema and no schema descriptions, the definition is incomplete: it explains high-level merge behavior but leaves most parameter semantics and invocation details unaddressed. An agent would still lack enough information to call this correctly in many scenarios.

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 26 parameters and 0% schema description coverage, the description must carry parameter meaning, but it only clarifies the mode values and the general idea of adjudication/resolution. Central parameters such as baseDoc, oursDoc, theirsDoc, previewHash, idempotencyKey, and actor remain 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?

The description states a specific verb and resource: a three-way structured merge for the same project or external JSON/RP1 files, with preview/apply/check-external modes. It is clear, though it does not explicitly contrast itself with sibling tools such as studio_apply_commands or studio_undo.

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?

It identifies usage contexts (concurrent human/AI edits and external file merges) and names the three modes, but does not explain when to choose preview, apply, or check-external, nor when not to use this tool. Guidance is implied rather than explicit.

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