Skip to main content
Glama

rebind_widgets

Filter widgets and batch-bind existing native styles in the file, with an option to explicitly clear local style overrides.

Instructions

筛选元件并批量绑定文件中已有原生样式;可显式清除局部样式覆盖。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node rebind-widgets.mjs <source.rp|rplib> <output.rp|rplib> <selector.json> [--reset-overrides]

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare it is a non-read-only, non-destructive, closed-world mutation, so the description's job is to add the details annotations cannot carry. It does: the opt-in clearing of local style overrides via --reset-overrides, the session-chain behavior for implicit vs. explicit source/output, and the evidence/verification restriction tied to gui-roundtrip. It stops short of saying whether cleared overrides are recoverable or what happens to widgets that match no style.

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 action and the optional override-clearing, then the invocation-mode rules, then the evidence caveat and CLI form. Every sentence carries information, though the chain semantics sentence is dense and telegraphic, and the CLI line partially duplicates what the schema already expresses. Slightly more structure would make the two invocation branches easier to scan.

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 mutation tool with no output schema, the definition covers the mutation surface, the session-chain contract, and a verification caveat, which is most of what an agent needs. Remaining gaps are the selector file format and any indication of what the call returns or how many widgets were rebound. These are meaningful but secondary given the annotations already cover the safety profile.

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 coverage is already 100%, so the schema carries most of the parameter burden and the baseline is 3. The description does add genuine meaning for the second oneOf branch (session:true means args omit host source and output, and multi-source tools still pass the import source) plus the --reset-overrides CLI equivalent. It adds nothing about the selector parameter's expected JSON shape, which is the least self-explanatory input.

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 concrete verb pair and resource: filter widgets and batch-bind existing native styles in the file, with an optional explicit clearing of local style overrides. That is far more specific than a restatement of the name. It does not, however, contrast itself with plausible siblings such as explain_binding or list_custom_styles, so an agent still has to infer which tool to reach for.

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 does explain the two invocation modes (named call omitting host source/output vs. raw args with session:true) and the rule that explicit paths do not advance the chain, which is real routing guidance. What is missing is when to use this tool rather than a sibling, or when not to use it at all beyond the caveat that it only applies to verified samples in capabilities.md. Usage is implied by context rather than stated as a selection rule.

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