Skip to main content
Glama

axure_open

Opens an editing session by validating a source .rp file, creating a working copy, and returning a project overview for AI-driven design revisions.

Instructions

开启编辑会话:红线检查源 .rp → 复制出工作副本链[0](与源同目录,源主名.work-1.rp)→ 返回总览(页面清单/元件数/交互数、全局变量、母版、结构三零)。每连接一个会话;再次 open 换源重建。

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

Input Schema

NameRequiredDescriptionDefault
rpNo
fileNo
pathNo
rpFileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important side effects: redline-checking the source, creating a work copy in the same directory with a .work-1.rp naming convention, and returning an overview of pages, widgets, interactions, global variables, and masters. It also explains session lifecycle behavior, though it omits error and permission 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 compact and front-loaded, using an arrow-based workflow summary to convey the main sequence efficiently. It is dense but not padded with unnecessary wording.

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 stateful tool with four undocumented parameters and no output schema, the description covers the workflow and return overview but leaves a critical gap in parameter semantics and source selection. An agent still cannot determine from the definition which parameter to use to supply the .rp file.

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

Parameters1/5

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

The input schema has four string parameters (rp, file, path, rpFile) with 0% description coverage, yet the tool description does not identify which parameter supplies the source .rp or explain whether the parameters are aliases, mutually exclusive, or otherwise related. This leaves the caller unable to map the description 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?

The description states a specific operation: opening an editing session, checking the source .rp, copying a working copy, and returning an overview. It is clearly more than a restatement of the name, but it does not explicitly differentiate itself from sibling tools such as studio_open_project.

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 gives some usage context by stating that there is one session per connection and that opening again switches source and rebuilds. However, it does not say when to use this tool versus alternatives, nor does it clarify prerequisites or which parameter selects the source.

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