Skip to main content
Glama

clone_library_widget

Clones one native control from an .rplib library into a target .rp page, using session chaining or explicit source and output paths.

Instructions

从 .rplib 克隆单个原生控件到目标 .rp 页面。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node clone-library-widget.mjs <source.rplib> <target.rp> <output.rp> [--x N --y N --w N --h N]

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses real behavior: explicit paths do not advance the session chain, session mode injects host source and output, and multi-source tools retain the import source. It also scopes applicability to samples verified in capabilities.md with gui-roundtrip evidence, though it says nothing about what gets written or returned when the clone succeeds or fails.

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 text is front-loaded with the core action, then mode rules, then the CLI signature, with no filler sentences. It is dense and jargon-heavy ('登记证据 gui-roundtrip', '核心链'), which slows parsing slightly but each clause carries operational information.

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 file-mutating clone operation with no output schema and one of two parameters documented in the schema, the description covers source/target semantics, argument ordering, session-mode rules, and applicability limits. It stops short of stating what the output .rp contains or what happens on name collisions, which would matter for a write tool.

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 only 50% schema coverage, the CLI line does heavy lifting by pinning the positional order inside the args array (<source.rplib> <target.rp> <output.rp> <sourcePage> <targetPage> <newName>) plus the optional --x/--y/--w/--h geometry flags, and it explains that multi-source tools still pass the import source. It does not clarify whether those flags are literal array elements or how they are encoded, so the mapping to args remains slightly ambiguous.

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 gives a concrete verb and resource: clone a single native widget ('单个原生控件') from a .rplib into a target .rp page. The qualifier '单个' implicitly contrasts with page-level cloning siblings such as clone_library_page_content, but no sibling is named explicitly, which keeps this just short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear conditional usage for the two invocation modes: named calls that omit host source/output ride the session chain, while raw args require session:true and omitting those two parameters; it also warns that explicit paths do not advance the chain. What's missing is guidance on when to pick this tool over sibling clone tools rather than over invocation modes.

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