Skip to main content
Glama

desktop_clear

Clears a resolved UI element's value to an empty string, letting desktop automation agents reset text fields before entering new input.

Instructions

agent-desktop clear: Clear element value to empty string

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

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 supplied, so the description carries the full disclosure burden. It implies a mutation but never states whether the prior value is recoverable, whether the element must be editable or focused, how non-text widgets respond, or what a success/failure result looks like. For a no-annotation mutation tool this is a substantial gap.

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 clauses. The "agent-desktop clear:" prefix is redundant with the tool name and consumes a third of the text without adding information.

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?

With no annotations and no output schema, the description is the only place to learn behavior, and it leaves out element-editability requirements, focus expectations, and failure semantics. The schema covers the inputs, but the behavioral side is under-described for a mutation 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 ref_id and timeout_ms fully documented in the schema, so the baseline is 3. The description adds no extra meaning about ref_id format or how timeout interacts with the clear action beyond what the schema already says.

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?

"Clear element value to empty string" gives a specific verb and a specific effect, and the word "element" implicitly separates it from desktop_clipboard_clear. It stops short of naming that sibling or specifying which element kinds this applies to, so an agent must infer the distinction.

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?

There is no guidance on when to use this instead of typing an empty string via keyboard tools, no prerequisites (e.g. element must be focused or editable), and no named alternatives. The only usage cue is the implicit read of the verb.

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