Skip to main content
Glama

gui_roundtrip

Copies an Axure project to a new file and reopens it in Axure RP 9/11 to validate native save/load behavior, optionally triggering and verifying local preview.

Instructions

复制到新文件后在 Axure RP 9 或 RP 11 保存、关闭、重开(宿主按 version 或源文件版本绑定;macOS 走 Swift 宿主,Windows 走 PowerShell 宿主);可选传 preview=true 在重开后触发预览并校验本地预览地址。默认立即返回 job 句柄。

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": {
      "source": "<source>",
      "output": "<output>"
    },
    "name": "gui_roundtrip"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
outputYes
sourceYes
previewNo可选:重开后是否触发 Axure 原生菜单「发布 -> 预览 / Publish -> Preview」启动本地预览,默认 false
versionNo目标 Axure 版本;省略时用源文件头版本

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses platform-specific hosts (Swift on macOS, PowerShell on Windows), version binding behavior, that the source is copied rather than mutated in place, and that the default return is a job handle rather than a completed result. Remaining gaps are permissions/auth requirements and how to poll the job, but the async model is surfaced, which is the key behavioral fact.

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 semicolon-delimited sentence that front-loads the core operation and then layers in host, preview, and return-mode details. Every clause carries information, though the density makes it harder to scan than a short bulleted structure would.

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 5-parameter tool with no annotations and no output schema, the description covers the critical unknowns: the async job-handle return (necessary since no output schema exists), platform host differences, and the optional preview verification step. It does not state whether the output file is overwritten or what job states mean, but the essential calling information is present.

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 only 40%, so the description must compensate. It explains preview and version semantics (version falls back to the source file header version) and implies wait via 'returns a job handle immediately by default'. It adds nothing about source vs output path semantics beyond the schema's minLength constraints, leaving part of the coverage gap unaddressed.

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 concrete operation sequence: copy to a new file, then save/close/reopen in Axure RP 9 or RP 11, with optional preview verification. The verb chain and target application are specific enough to distinguish it from sibling tools such as axure_open or axure_save. It stops short of explicitly naming those siblings as alternatives, which keeps it from a 5.

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 implied usage is clear from the described workflow (roundtrip verification), and preview=true is framed as optional. However, there is no explicit statement of when to use this instead of axure_open/axure_save, no prerequisites, and no exclusions. The guidance is inferable but not spelled out.

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