Skip to main content
Glama
Sign In
windows2-mcp

windows2-mcp

by verisoft-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_from_selection

Remove an item from the current selection in a multi-select UI container by providing the element ID from a previous search.

Instructions

Remove an item from the current selection in a multi-select container via the UIA SelectionItem pattern.

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>"
    },
    "name": "remove_from_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementIdYesElement ID returned by find_element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose side effects (e.g., whether selection state changes immediately, whether the container must support multi-select, or error conditions like attempting removal on single-select). The reference to 'UIA SelectionItem pattern' hints at automation behavior but lacks explicit behavioral context.

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, front-loaded sentence with no extraneous words. Every word adds value, making it highly concise.

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?

Given the tool has one parameter and no output schema, the description covers the core purpose. However, it lacks details on prerequisites (e.g., container must support multi-select) and error handling, which are important for an interactive automation tool.

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% with one required parameter 'elementId' described as 'Element ID returned by find_element'. The description does not add new semantics beyond the schema; it merely states the parameter's role implicitly.

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 description clearly states the action ('Remove an item from the current selection'), the context ('multi-select container'), and the mechanism ('UIA SelectionItem pattern'). It distinguishes from sibling tools like 'add_to_selection' and 'get_selected_item'.

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 implies usage when an item is selected in a multi-select container, but does not explicitly state when to use this tool versus alternatives like 'clear_element' or 'click to deselect'. No prerequisites or fallback guidance is provided.

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