Skip to main content
Glama

create_panel_clone

Clone an existing template offline to create a dynamic panel and insert a state package, using session context to omit source and output paths when needed.

Instructions

克隆真实模板离线创建动态面板并插入状态包。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node create-panel-clone.mjs <src.rp> <out.rp> [state...] [--x N --y N --w N --h N] [--page-index 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": "create_panel_clone"
  }
}

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?

Beyond the annotations, the description discloses important behavior: named invocation omits host source/output and uses the session chain, raw args use session:true, explicit paths do not advance the chain, and multi-source tools retain the import source. It also adds an evidence/verification constraint tied to capabilities.md, though it does not spell out return behavior or permissions.

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 dense but front-loads the purpose before giving session-chain rules, evidence constraints, and CLI syntax. Every clause carries operational information, though the telegraphic phrasing and mixed concepts make it less immediately scannable than it could be.

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 create tool with no output schema, the description covers the main calling mechanics, session behavior, and evidence restriction. It still leaves gaps around what is returned, what a 'state package' contains, and how errors or partial failures behave, which are relevant for a non-readOnly creation 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?

The schema only defines args as a string array and session as a boolean, with 50% description coverage. The description compensates by documenting the CLI positional order (<src.rp> <out.rp> <pageName> <panelName> [state...]) and optional flags, and by explaining how session:true changes which args are omitted. It does not fully explain state-string semantics, but it adds substantial meaning beyond 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 verb and resource: cloning a real template offline to create a dynamic panel and insert state packages. It is clear enough to distinguish the core action, but it does not explicitly differentiate itself from siblings like create_blank_page, clone_library_widget, or fill_panel_state.

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 operational guidance for session-chain usage and raw args, plus a restriction that it only applies to verified samples in capabilities.md. However, it does not explicitly say when to use this tool versus related alternatives such as create_blank_page or fill_panel_state, leaving selection guidance implied rather than stated.

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