Skip to main content
Glama

desktop_toggle

Toggle a checkbox or switch in a desktop interface by supplying its snapshot reference, enabling agents to change UI state and verify the resulting condition.

Instructions

agent-desktop toggle: Toggle a checkbox or switch

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_toggle"
  }
}

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

C2.9/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 the full behavioral burden, and it discloses almost nothing beyond the mutation itself. It does not say whether the resulting state is returned, what happens with a stale or unresolved ref, whether the action is retried within the timeout, or whether it fails on non-checkbox elements.

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?

The single sentence is front-loaded and wastes no words, though the "agent-desktop toggle:" prefix largely repeats the tool name rather than adding information. The terseness is efficient but borders on under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating UI-action tool with zero annotations and no output schema, the description should explain return behavior, failure modes, and the snapshot-ref workflow. As written, an agent can guess what it does but not how it behaves or what to expect on success or failure.

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%, with ref_id and timeout_ms fully documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as whether the ref must come from a specific snapshot or how timeout_ms interacts with toggling.

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?

States a specific verb ("Toggle") and resource ("a checkbox or switch"), so an agent knows exactly what element type is targeted and what action occurs. It does not, however, distinguish itself from siblings like desktop_check, desktop_is, or desktop_click, which plausibly also interact with checkboxes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no exclusions, and no mention of alternatives such as desktop_check (presumably for reading state) or desktop_click. The only implicit signal is the target element type, leaving the agent to infer that this is the correct tool for changing a checkbox's state.

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