AI Process Manager

Overview Schema Source Related Servers Discussions Admin

ui_set_value

Destructive

Set text directly in an editable field using UI Automation, eliminating key simulation. Requires action tier and allowlist; check field visibility before use.

Instructions

Set text in an editable field via UI Automation (no key simulation). REQUIRES action tier + allowlist. Check can_set_value in ui_find; modern apps (e.g. Win11 Notepad) may not expose fields. Confirm with the user first.

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": {
      "value": "<value>"
    },
    "name": "ui_set_value"
  }
}

Input Schema

Name	Required	Description
`hwnd`	No	Exact window handle
`value`	Yes	Text to set
`element_index`	No	Stable index from ui_find
`name_contains`	No	Field name
`title_contains`	No	Window title fragment

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower. The description adds valuable context: the action-tier/allowlist requirement, the method (UI Automation, no key simulation), the limitation with modern apps (e.g., Win11 Notepad), and the recommendation to confirm with the user. This goes beyond annotations without contradicting them.

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?

The description is three sentences, front-loads the core purpose, and each sentence contributes essential information: what it does, requirements, caveats, and user confirmation. No wasted words, and the structure is clear and scannable.

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 5 parameters, no output schema, and annotations present, the description covers the core purpose, requirements, limitations, and a usage precheck. It doesn't describe error behavior or return values, but given the tool's simplicity and the annotations, this is reasonably complete. A brief note on success/failure output would make it fully 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 100%, so the baseline is 3. The description adds minimal extra meaning beyond the schema: it clarifies that the value is set via UI Automation and mentions field exposure issues, but doesn't elaborate on individual parameters. The schema already documents all five parameters adequately.

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?

The description clearly states the tool's function: 'Set text in an editable field via UI Automation.' It uses a specific verb ('Set') and resource ('editable field'), and distinguishes from siblings by noting it does not use key simulation and referencing ui_find as a precheck. This makes the purpose unambiguous and distinct from related tools.

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 provides clear usage context: it requires action tier + allowlist, instructs to check can_set_value in ui_find, warns that modern apps may not expose fields, and advises confirming with the user first. While it doesn't explicitly name alternatives for non-text actions, it gives strong when-to-use guidance and prerequisites.

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