Skip to main content
Glama

desktop_collapse

Collapse a disclosure triangle or tree item by its accessibility ref to hide nested content and reduce visible UI in desktop automation.

Instructions

agent-desktop collapse: Collapse 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_collapse"
  }
}

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

B3.1/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 adds nothing about whether the collapse is idempotent, what happens if the target is already collapsed, whether a snapshot becomes stale afterward, or what failure modes exist. The only behavioral hints (timeout, actionability wait) come from the schema, not the description.

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?

Single front-loaded sentence with no filler; only waste is the redundant "agent-desktop collapse:" prefix that repeats the tool name. Appropriate length for a two-parameter action.

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?

A mutation tool with zero annotation coverage, no output schema, and an implicit dependency on a prior snapshot is under-described. An agent cannot tell from the description whether state persists, whether it needs a re-snapshot, or how errors surface.

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 both documented, so the baseline is 3. The description adds no meaning beyond the schema, such as whether a stale ref_id is auto-refreshed or how ref qualification interacts with collapsing.

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 ("Collapse") and specific target objects ("a disclosure triangle or tree item"), so the action is unambiguous. It does not name or contrast with the obvious counterpart, desktop_expand, but the verb/resource pair is still clear enough to distinguish it without opening the schema.

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?

Usage is only implied: an agent can infer it applies to expanded disclosures or tree items. There is no explicit guidance on when to prefer this over desktop_expand or desktop_click, and no stated prerequisites such as needing a fresh snapshot.

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