Skip to main content
Glama

set_widget_geometry

Update widget position and size (x, y, width, height) individually or in batches to adjust layouts; changes can sync back to RP/1 source.

Instructions

快捷修改元件几何位置与尺寸(x、y、w/width、h/height):定位(target 或 widget+page)→ 更新二进制 MyStyle 坐标与尺寸(DOAName 3221225573 / 3221225577)→ 写新链节点并校验三零。支持单条或 edits 批量修改,改动可被 sync_prototype(lift/merge) 自动导回 RP/1 源码。

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

Input Schema

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

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?

Even though annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, the description adds real behavioral content: it mutates binary MyStyle coordinates under specific DOANames, writes a new chain node, runs a '三零' validation, and notes the result can be pulled back into RP/1 source via sync_prototype(lift/merge). That round-trip consequence is exactly the kind of context annotations cannot convey. It does not describe failure modes or what happens when the locator matches more than one widget.

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?

One dense, front-loaded sentence built as an arrow-separated pipeline (locate → update → write/validate), with the batch option and round-trip caveat appended. Nothing is redundant, but internal identifiers ('DOAName 3221225573 / 3221225577', '三零') consume space without helping the agent decide or call correctly.

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 10-parameter mutation tool with 10% schema coverage and no output schema, the description covers the main workflow and most parameter intent, which is reasonable. The critical gap is that no parameters are required, yet the description never states that at least one locator (target or widget+page) must be supplied for a call to make sense. It also omits what the validation result or error looks like.

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 10%, so the description has to carry meaning, and it does partially: it maps the shorthand aliases (w/width, h/height) and explains the two locator paths of 'target 或 widget+page' plus the batch 'edits' array. However, the alias equivalence and the target/watch shapes are largely already spelled out inside the schema's target property description, so the description adds only modest new meaning. The 'edits' item structure and the page scoping are not explained beyond the parenthetical.

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 leads with a specific verb-plus-resource pair ('快捷修改元件几何位置与尺寸') and enumerates exactly which attributes it touches (x, y, w/width, h/height), which cleanly separates it from siblings like set_widget_style, set_widget_text and set_widget_richtext. It stops short of naming any sibling as a contrast case, so an agent must infer the boundary rather than being told it.

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?

Usage is implied through the described workflow (locate via target or widget+page, then update) and through '支持单条或 edits 批量修改', which tells the agent the single-vs-batch choice exists. There is no explicit when-not guidance, no statement of prerequisites (e.g. that a unique target is required), and no pointer to an alternative tool for geometry changes.

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