Skip to main content
Glama

desktop_set_value

Sets the value of a resolved desktop UI element via its accessibility attribute to fill fields or update controls without keystroke simulation.

Instructions

agent-desktop set-value: Set element value directly via accessibility attribute

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

Input Schema

NameRequiredDescriptionDefault
valueNoValue to set
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 behavioral burden, yet it discloses only the access mechanism. It does not say whether the target must be an editable/focusable element, whether the previous value is lost, what happens on failure or unsupported elements, or what the response contains.

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 clause, front-loaded, with no filler. Brevity is appropriate in form, though the terseness leaves gaps that structure alone cannot offset.

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 parameterless-annotation mutation tool with no output schema, the definition is too thin: an agent knows what it does but not when it will fail, what it requires of the target element, or how success is signaled.

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, value, and timeout_ms are already documented with formats and defaults. The description adds only the mechanism note, which gives marginal context for why setting may fail; 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?

States a concrete verb and resource: set an element's value directly via an accessibility attribute. The mechanism ('accessibility attribute') distinguishes it from synthetic-input siblings like desktop_click or keyboard tools, though no sibling is named explicitly.

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 says what it does but never states when to prefer it over alternatives such as desktop_get (for reads), desktop_click/keyboard input, or desktop_batch. No preconditions or exclusions are given.

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