Skip to main content
Glama

fill_panel_state

Imports a page's controls into a Page or Master PanelState, with append/replace modes and support for nested panels, repeaters, masters, and connector anchors.

Instructions

把一个 Page 的控件闭包导入 Page 或 Master 所属 PanelState(支持 --master、--append/--replace、嵌套面板/中继器/母版/连接线自定义锚点及闭合内部交互)。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node fill-panel-state.mjs <source.rp> <target.rp> <new.rp> [--master] [--append | --replace]

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only assert readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description goes meaningfully beyond them by disclosing session-chain advancement semantics, the multi-source import-source exception, and a verification gate ('只适用 capabilities.md 的已验样本'). The CLI signature also reveals a three-file model in which the result goes to a separate new.rp rather than mutating the target in place, which matters for an agent assessing side effects. It stops short of saying what --replace does to pre-existing PanelState content, which is the one behavior an agent most needs before a destructive-looking write.

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 single dense run-on with stacked parentheticals mixing feature list, session semantics, evidence-gating, and a raw CLI usage string. Each element is relevant, yet the lack of separation makes it slower to parse than it needs to be. The CLI line in particular could be dropped or isolated since the schema supersedes it.

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 complex two-form tool with no output schema, the description covers the two invocation shapes, master targeting, append/replace modes, nesting support, and a verification constraint. What remains thin is outcome behavior: nothing says whether --replace discards existing state content or how the separate new.rp output relates to the target file. Given the annotations are sparse, that omission keeps it from a 5.

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 description coverage is 100%, so the object form including targetMaster/targetPage mutual exclusivity and the session flag is already documented in the schema; baseline 3 applies. The description adds some value by explaining the args/session variant and implicitly mapping CLI positionals to source/target/output, but it does not clarify whether the positional CLI string is meant literally when the schema is object-shaped, which risks mild confusion. Net, it roughly matches rather than exceeds what the schema already conveys.

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 opening clause names a specific verb and resource: importing a Page's widget closure into a PanelState owned by a Page or Master, and it enumerates supported sub-features (nested panels/repeaters/masters, connector anchors, closed internal interactions). It is clearly distinguishable from the sibling remove_panel_state_content. It does not explicitly name an alternative for the reverse or removal case, keeping it just short of 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?

It gives concrete invocation-mode guidance: named calls may omit host source/output to use the session chain, raw-args form must use session:true, and explicit paths do not advance the chain. However, it never states when to prefer this tool over siblings such as create_panel_clone or axure_state, and it gives no when-not-to-use conditions. The usage information present is about syntax modes rather than tool selection.

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