Skip to main content
Glama
Sign In
windows2-mcp

windows2-mcp

by verisoft-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_element_value

Update the value of a UI element like a slider or spin box by providing its element ID and the new value.

Instructions

Set the value of an element via the UIA Value or RangeValue pattern (e.g. sliders, spin boxes).

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

Input Schema

NameRequiredDescriptionDefault
valueYesThe value to set
elementIdYesElement ID returned by find_element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide destructiveHint=false, indicating a safe operation. The description adds the UIA pattern context, but does not mention prerequisites (e.g., element must be enabled, visible) or potential side effects. It adds some value beyond annotations but not extensive detail.

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 a single, focused sentence of 14 words. It immediately conveys the core action and mechanism with examples. No extraneous words; every phrase earns its place.

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?

Given the tool's simplicity (2 parameters, no output schema), the description adequately covers the purpose and mechanism. It could briefly mention return behavior or error conditions, but is largely complete for an agent to understand the tool's role.

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% (both parameters described in schema). The description does not add additional semantic information about parameter values, formats, or constraints. Baseline is 3 due to high schema coverage, and no extra info is provided.

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 core action ('Set the value of an element'), the specific UI automation pattern used ('UIA Value or RangeValue pattern'), and concrete examples ('sliders, spin boxes'). This effectively differentiates it from sibling tools like 'set_value' or 'click_element'.

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 strong cues about when to use the tool by mentioning the specific patterns and examples. However, it lacks explicit guidance on when not to use it (e.g., for standard input fields where 'send_keys' may be more appropriate) or mention of alternatives.

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