Skip to main content
Glama

desktop_select

Selects an option in a list or dropdown using a snapshot ref ID, enabling precise UI interaction and post-action verification.

Instructions

agent-desktop select: Select an option in a list or dropdown

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>",
      "value": "<value>"
    },
    "name": "desktop_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesOption to select
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.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the action. It does not say whether selection requires the list to be visible, whether it scrolls to find options, what side effects it triggers, or what happens if the ref is stale or unresolvable.

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 description is a single front-loaded sentence with no filler. The 'agent-desktop select:' prefix redundantly repeats the tool name, which is the only minor structural waste.

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 UI-mutating selection tool with no annotations and no output schema, the description is too thin. It should at least explain whether the target list must be open, how refs are resolved, and what a successful versus failed selection looks like.

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 the schema already documents value, ref_id, and timeout_ms in detail. The description adds no additional parameter meaning or format guidance beyond the schema, which is the expected baseline when coverage is complete.

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 names a specific verb and resource: 'Select an option in a list or dropdown.' It is clear what the tool does, though it does not differentiate itself from siblings such as desktop_click or desktop_find.

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?

The phrase 'in a list or dropdown' implies the scenario where this tool applies, suggesting it is for choosing from native list/dropdown options rather than arbitrary clicking. However, there is no explicit when-to-use guidance, no mention of alternatives like desktop_click, and no stated prerequisites such as whether the dropdown must already be open.

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