Skip to main content
Glama

name_widget

Rename Axure RP widgets by old name with an optional page, or by record/object ID, while preserving widget identity and interactions.

Instructions

按旧名称快捷改名(可加页名),或按记录/对象 ID 精确改名;保留身份与交互。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 preview,只适用 capabilities.md 的已验样本。CLI: node name-widget.mjs <source.rp> <new.rp> --name --to [--page ];或 --record --widget --to ;兼容 <pageRecordsIndex|页名> [...]

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

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?

The annotations already mark this as a non-read-only, non-destructive, closed-world operation. The description adds valuable behavior beyond them: renaming preserves identity and interactions, named calls use the session chain, explicit paths do not advance the chain, and evidence preview is limited to verified samples. It does not cover collision or failure behavior, but the added context is substantial.

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, and most clauses carry useful information, but the description is a dense run-on with semicolon-separated concepts and a long CLI line. The capabilities.md constraint is obscure, making the definition harder to scan than necessary.

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 moderately simple rename mutation with no output schema, the description covers both identification modes, preservation guarantees, session-chain behavior, and CLI invocation. It still leaves error/collision behavior and sibling selection unaddressed, but it is largely complete for correct invocation.

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 description coverage, the description compensates by mapping the args array to concrete forms: --name/--to/--page or --record/--widget/--to, plus positional compatibility. It also explains session:true omitting host source and output, though the relationship between the CLI-style flags and the JSON args array could be clearer.

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?

It states a specific verb and resource: rename a widget by old name (optionally with page name) or precisely by record/object ID, while preserving identity and interactions. This is clear, but it does not distinguish the tool from the sibling rename_widget, so it falls 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 Guidelines3/5

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

The description explains the two renaming modes and some session-chain conditions, which implies usage. However, it never says when to choose this over rename_widget or other widget tools, and it gives no explicit 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