Skip to main content
Glama

create_blank_page

Appends a same-version blank template page to an existing Axure .rp file to create a new blank page for design work; cross-version templates are rejected.

Instructions

把与输入文件同版本的空白模板 Page 记录追加到已有 .rp 生成新空白页(跨版本模板会拒绝)。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node create-blank-page.mjs <input.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_blank_page"
  }
}

Input Schema

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

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?

Annotations already declare a non-read-only, non-destructive, closed-world mutation. Beyond that, the description discloses a concrete failure mode (cross-version templates are rejected) and that the operation appends to an existing .rp rather than producing a new file. It stops short of describing behavior when the page name already exists or 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.

Conciseness3/5

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

The purpose is front-loaded, which is good, but the body is a dense run of semicolon-joined clauses mixing invocation modes, chain semantics, and internal evidence bookkeeping ('登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本'). That last clause is validation metadata of marginal value to an invoking agent and dilutes the actionable content.

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 two-parameter mutation with no output schema, the description covers purpose, the version constraint, both invocation modes, and the argument order, which is enough to call it correctly. The remaining gap is return/conflict semantics, minor given annotations already flag the operation as safe-but-mutating.

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?

Schema coverage is 50%, and only the session flag is documented in-schema. The description compensates by spelling out the args ordering via the CLI form (<input.rp> <output.rp> <newPageName>) and by explaining exactly what session:true changes and what must be omitted when it is set.

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?

States a specific verb and resource — appends a blank template Page record to an existing .rp to create a new page — and adds the qualifier that the template must be the same version as the input file. This distinguishes it implicitly from duplicate_page/clone_library_page_content, though no sibling is named explicitly.

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?

Gives real invocation guidance: named invocation omits host source/output to use the session chain, raw args require session:true with those two params omitted, and explicit paths do not advance the chain. However, it never says when to choose this over duplicate_page or create_blank_project, so alternative selection is left to inference.

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