Skip to main content
Glama

desktop_check

Set a desktop checkbox or switch to the checked state using a snapshot ref, idempotently, so repeated calls keep the control checked.

Instructions

agent-desktop check: Set checkbox or switch to checked 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_check"
  }
}

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, the description carries the full burden. It usefully discloses idempotency (re-calling on an already-checked control is harmless), which is real behavioral context beyond the name. However, it says nothing about failure modes when the ref does not resolve to a checkable element, whether it errors or no-ops, or what side effects occur.

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, front-loaded with the action and target. The "agent-desktop check:" prefix is redundant with the tool name and slightly dilutes the opening, but there is no other waste.

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 mutation tool with no output schema, the description covers the core action and idempotency. It is still thin on what happens with non-checkable refs and on the relationship to desktop_clear, which a calling agent would want before invoking it.

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 both ref_id and timeout_ms are already documented in the schema, setting the baseline at 3. The description adds no additional constraint, such as requiring the ref to point at a checkbox or switch rather than any element, so it does not exceed the baseline.

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 gives a specific verb and target ("Set checkbox or switch to checked state"), which is clear enough for an agent to understand the operation. It does not distinguish itself from the many siblings, notably desktop_click (could plausibly toggle a checkbox) or desktop_clear (likely the inverse), leaving the boundary implicit.

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 only: it applies to checkbox/switch elements that need to be in the checked state. There is no explicit statement about when to prefer this over desktop_click, or when to use desktop_clear instead. The word "idempotent" hints that it is safe to call when already checked, but that is the only guidance.

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