Skip to main content
Glama

rename_widget

Rename widgets in Axure prototypes by target name or located ID, including batch edits across pages, panel states, repeater templates, and masters while preserving text and interactions.

Instructions

快捷改名:target 为名称/文本或 locate 的 record+id,name(或 newName)为新名称;edits 可批量修改。覆盖页面、面板状态、中继器模板和母版定义。只改元件名,保留文字、身份与交互;允许重名,目标歧义时返回候选。全部成功后提交一个新链节点。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rename_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pageNo
editsNo
targetNolocate 返回的定位字段对象(record+id [+container] 精确定位)或 {query[,page][,type]} 搜索(须唯一)或字符串(按名称/文本搜)
widgetNo
newNameNo

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?

Beyond the annotations (which only say non-read-only, non-destructive, closed-world), the description discloses that text, identity and interactions are preserved, that duplicate names are permitted, that ambiguous targets return candidates instead of mutating, and that a chain node is committed only after all edits succeed. These are genuine behavioral facts an agent could not infer from the annotations alone.

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?

Front-loaded with the operation and target format, then behavior, then transactional semantics - a sensible order with no filler. The semicolon-chained clauses are dense and would read more clearly as distinct sentences.

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 mutation tool with no output schema, the description covers preservation guarantees, ambiguity handling and commit semantics well, but never says what an agent sees on conflict (candidate list format) or how the unmentioned page/widget parameters interact with target. Adequate, not complete.

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 only 17%, so the description has to carry the load. It explains target formats (locate's record+id vs. name/text search), the name/newName aliasing, and edits as a batch list, but leaves the page, widget and edits[].widget parameters unaddressed.

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 first clause states a specific verb and resource - quick rename of a widget - and the description enumerates the scope it covers (pages, panel states, repeater templates, master definitions). It never contrasts itself with the sibling name_widget, so an agent cannot rule out the near-duplicate without opening both schemas.

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 states the two accepted target forms and that edits is for batch modification, which implies when each path is appropriate. It gives no explicit when-not condition and does not name any alternative tool, leaving the choice between this and name_widget 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