Skip to main content
Glama

desktop_uncheck

Sets a checkbox or switch to its unchecked state using a qualified snapshot ref, with idempotent behavior for reliable desktop UI automation.

Instructions

agent-desktop uncheck: Set checkbox or switch to unchecked state (idempotent)

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": {
      "ref_id": "<ref_id>"
    },
    "name": "desktop_uncheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
ref_idYesQualified ref from snapshot (@<snapshot_id>:eN)
timeout_msNoMaximum ref-resolution and transient-actionability wait in milliseconds; terminal failures return immediately

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does add one valuable trait, that the operation is idempotent, but says nothing about what happens with a non-toggle element, how failures surface, or whether state changes are reversible.

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

Conciseness4/5

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

A single short sentence with the action front-loaded and no wasted wording. The leading 'agent-desktop uncheck:' prefix is mildly redundant with the tool name but harmless.

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?

For a simple two-parameter toggle tool with a fully documented schema and no output schema, this is close to adequate. The main omission is failure behavior, such as what happens when the referenced element is not a checkbox or switch.

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 ref_id (qualified snapshot reference) and timeout_ms are already fully documented in the schema. The description adds nothing about parameter meaning; baseline 3 applies.

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 states a specific verb and resource: setting a checkbox or switch to the unchecked state. It is clear what the tool does, and the uncheck/check pairing with the sibling desktop_check is implied by the wording rather than spelled out.

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?

Usage is implied: call this when a control should end in the unchecked state. There is no explicit when-to-use or when-not guidance, and no mention of using desktop_check for the opposite transition or of ref_id needing to come from a fresh snapshot.

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