Skip to main content
Glama

create_master

Duplicates an existing Axure Master record and registers the copy as a new named master, enabling reusable master variants while session mode can inject source and output paths.

Instructions

复制已有 Axure:Master 记录并注册为新命名的母版。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 preview,只适用 capabilities.md 的已验样本。CLI: node create-master.mjs <source.rp> <output.rp>

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": {
      "args": "<args>"
    },
    "name": "create_master"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes
sessionNotrue 时 args 省略宿主源和输出,由当前链注入;多源工具仍传导入源。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare that this is a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds real behavioral detail beyond them, namely that explicit paths do not advance the session chain and that the registration evidence is 'preview' and valid only for verified samples in capabilities.md. It still omits what happens on name collision, whether the source master is modified, and what is returned.

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 purpose is front-loaded in the first sentence, and each subsequent sentence carries distinct information (mode selection, chain behavior, the evidence restriction, and the CLI mapping). The telegraphic, jargon-dense phrasing ('登记证据 preview,只适用 capabilities.md') makes it harder to parse, but no sentence is pure filler.

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

Completeness3/5

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

For a mutating tool with no output schema and only partial schema coverage, the definition covers the invocation modes, the chain semantics, and the CLI argument order, which is substantial. It remains incomplete on failure behavior, naming collisions, and what a successful registration returns, which an agent would need before calling it confidently.

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?

With schema coverage at 50%, the args array is undocumented in the schema, but the description compensates by mapping it to four positional values in the CLI form: <source.rp> <output.rp> <SourceMasterName> <NewMasterName>, and by explaining which two of them to omit when session:true. The session parameter is already documented in the schema, so this outweighs the gap.

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 first clause gives a concrete verb and resource: 'copies an existing Axure:Master record and registers it as a newly named master', which tells an agent this is a copy-and-register operation, unlike siblings such as place_master or set_master_overrides. What holds it back from a 5 is the heavy session-chain jargon later in the text, which muddies the core action.

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 does give conditional guidance for the two invocation modes (named invocation omits host source/output and uses the session chain; raw args use session:true and omit both parameters) and warns that explicit paths do not advance the chain. However, it never says when to prefer this tool over siblings such as place_master, create_blank_project, or clone_library_widget, and it gives no when-not guidance.

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