Skip to main content
Glama

desktop_right_click

Triggers a right-click context menu on a resolved desktop UI element, either semantically or physically in headed mode, enabling access to element-specific actions.

Instructions

agent-desktop right-click: Open a context menu semantically, or physically with --headed

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

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.5/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, yet it does not explain what the two modes mean, whether headed mode is required, what a context menu appearing implies for follow-up calls, or what happens on failure. The only behavioral signal is the opaque '--headed' flag reference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short line with no wasted sentences, which helps, but it begins by restating the tool name and leans on unexplained jargon instead of front-loading clear actionable information. Brevity here reads as under-specification rather than precision.

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 two-parameter interaction tool with no annotations and no output schema, the description should state the expected post-condition (e.g. a context menu is open and must be interacted with via a ref) and mode requirements. It instead leaves the agent guessing what 'semantically' versus 'physically' means and what state results from the call.

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% and both parameters are documented in the schema, including the ref format and timeout semantics, so the baseline is met. The description adds no meaning beyond the schema about how ref_id or timeout_ms behave for a right-click specifically.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the action ('right-click') and the effect ('open a context menu'), so the resource is identifiable. However, 'semantically, or physically with --headed' is ambiguous internal jargon that does not resolve into a clear statement of what the tool actually does or how it differs from desktop_click or desktop_double_click.

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 explicit when-to-use guidance and no mention of alternatives among the many sibling click tools. The only usage hint is the vague 'semantically, or physically with --headed' distinction, which an agent cannot reliably act on without external knowledge.

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