Skip to main content
Glama

set_combobox_options

Updates the option list and selected item for a native ComboBox in Axure RP, optionally using session arguments when source and output paths are omitted.

Instructions

设置唯一原生 ComboBox 的选项与选中项。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node set-combobox-options.mjs <source.rp> <output.rp> [--selected ]

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

Input Schema

NameRequiredDescriptionDefault
argsYes
sessionNotrue 时 args 省略宿主源和输出,由当前链注入;多源工具仍传导入源。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare a non-read-only, non-destructive, closed-world mutation, and the description adds real behavior beyond them: only one native ComboBox is targeted, an explicit source/output path does not advance the session chain, and the tool is valid only for samples verified in capabilities.md. It still does not say whether the existing option list is replaced or appended, or what happens to the selection when an index is out of range.

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, but the body jumps between session-chain mechanics, an internal evidence tag ("登记证据 gui-roundtrip"), a capabilities-file caveat, and a CLI synopsis of limited relevance to an MCP caller. Nothing is redundant, yet the ordering makes the caller work to find the invocation contract.

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?

With only two parameters, no output schema, and annotations covering the safety profile, the definition covers invocation adequately. What it leaves out are the semantic outcomes an agent needs before calling: whether options are replaced wholesale, the accepted format of the options payload, and any error behavior for an invalid selected index.

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 only 50%: `session` is documented in-schema, while the required `args` array is undocumented. The description partially compensates by giving the positional order in the CLI form (<source.rp> <output.rp> <pageName> <widgetName> <options-json> [--selected <index>]), but it never states that these positions map one-to-one onto the `args` array, nor what shape the options JSON must take.

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 and resource: set the options and selected item of the single native ComboBox ("设置唯一原生 ComboBox 的选项与选中项"). That is specific enough to distinguish it from a generic widget editor, though it never contrasts itself with the sibling set_listbox_options, which the agent could easily confuse for ComboBox work.

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 invocation-mode guidance (named call omits host source/output and uses the session chain; raw args needs session:true), which implies when each form applies. But there is no explicit when-to-use versus the listbox/other set_* siblings, and no stated preconditions such as the ComboBox having to already exist on the page.

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