Skip to main content
Glama

desktop_expand

Expands a disclosure triangle or tree item using a qualified snapshot reference to reveal hidden child items in desktop accessibility trees.

Instructions

agent-desktop expand: Expand a disclosure triangle or tree item

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

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 disclosure burden, yet it only restates the action. It doesn't say what happens if the item is already expanded, whether stale refs produce an error, or whether the expansion is awaited/verified before returning.

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, front-loaded sentence with no wasted wording. The 'agent-desktop expand:' prefix duplicates the tool name and could be dropped, but the rest is efficient.

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 two-parameter, non-destructive UI action with no output schema, the essentials are covered by the schema. The gaps are behavioral: no indication of failure modes or state verification, which matters for an agent driving a live UI.

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 format and timeout_ms semantics documented in the schema itself, so the baseline of 3 applies. The description contributes nothing additional about either parameter.

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 (expand) and a specific resource (disclosure triangle or tree item), which is concrete enough that an agent can act on it. It doesn't explicitly name the inverse sibling desktop_collapse, but the action itself is unambiguous.

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 when-to-use guidance, no prerequisites, and no named alternative. In particular it doesn't say how this differs from clicking the same disclosure triangle with desktop_click, which is a real ambiguity for an agent.

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