TRAECNclaw MCP

Select TraeCN Setting Option

traecn_select_setting_option

Select and confirm a dropdown setting option using section, label, and a valid value returned by the option listing tool.

Instructions

Select one previously listed option for a dropdown setting identified by section and label, and confirm the applied selection. Only values returned by traecn_list_setting_options are valid.

Input Schema

Name	Required	Description
`label`	Yes	Setting label exactly as returned by traecn_list_settings.
`value`	Yes	Option value exactly as returned by traecn_list_setting_options.
`section`	Yes	Section name exactly as returned by traecn_list_setting_sections.

Output Schema

Name	Required	Description
`code`	No	Stable machine-readable result or error code.
`error`	No	Error identifier or diagnostic when the operation failed.
`label`	No	Setting label that was written.
`value`	No	Value applied to the setting.
`result`	No	Driver-reported write outcome, including already-in-desired-state.
`status`	No	Stable operation or task status.
`taskId`	No	Stable gateway task identifier.
`changed`	No	Whether visible TraeCN state changed.
`message`	No	Human-readable outcome summary.
`success`	No	Whether the operation succeeded.
`verified`	No	True only when the observed UI value equals the requested value.
`retryable`	No	Whether retrying the same call can succeed later.
`nextAction`	No	Suggested next step after a failure.
`controlType`	No	UI control whose value was read back.
`conversationId`	No	Stable TraeCN conversation identifier.
`requestedValue`	No	Value requested by the caller.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.7.1-glama.1Nov 7, 2026

addedOutput schema / properties / controlType

Added value: +{
+  "description": "UI control whose value was read back.",
+  "enum": [
+    "toggle",
+    "option",
+    "text"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / requestedValue

Added value: +{
+  "description": "Value requested by the caller."
+}

addedOutput schema / properties / verified

Added value: +{
+  "description": "True only when the observed UI value equals the requested value.",
+  "type": "boolean"
+}

First observedAug 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, and the description adds two real behavioral facts beyond them: invalid values are rejected (must come from traecn_list_setting_options) and the tool confirms the applied selection as a post-condition. It does not explain what happens on an invalid or stale value, nor whether re-selecting the same value has side effects, which matters given idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core action front-loaded and the validity constraint immediately after. Nothing is repeated from the title or schema verbatim.

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 three-parameter mutation with full schema coverage, annotations, and an output schema (so return values need not be described), the definition covers action, precondition, and validation constraint. The remaining gap is error/staleness behavior and explicit sibling routing, both minor at this complexity.

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 100% and all three parameters carry their own descriptions naming the exact source tool for each value. The description only reinforces that the value must come from traecn_list_setting_options, adding little beyond the schema. Baseline 3 applies when the schema already carries the semantic load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (select) and resource (one previously listed option for a dropdown setting), plus the two-part identifier (section + label). It is clearly separable from siblings like traecn_set_setting_toggle, traecn_set_setting_text, and traecn_select_model, since it is scoped to dropdown-type settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description establishes a prerequisite workflow: the option must have been 'previously listed' and only values from traecn_list_setting_options are valid. That implicitly tells the agent to call the list tool first and names the alternative data source. It does not explicitly state when to prefer this over traecn_set_setting_toggle or traecn_set_setting_text, leaving the 'dropdown vs toggle/text' routing to inference from the word 'dropdown'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.