Skip to main content
Glama

Right Click

right_click

Dispatches a right-click at specified x,y coordinates within the active window boundaries, enabling AI agents to open context menus and trigger secondary actions in Wayland GUI applications.

Instructions

Dispatches a right-click within the active window boundaries.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "right_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
pidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, non-open-world action. The description adds a useful scoping constraint ('within the active window boundaries'), but leaves key behavior unexplained: what happens if x/y fall outside those bounds, and whether the click is real input or synthetic dispatch with side effects.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the specification gaps noted in other dimensions.

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 three-parameter input tool with no schema descriptions and no output schema, the definition says too little. An agent cannot determine the coordinate frame, the semantics of the optional pid (app targeting?), or failure behavior when the coordinates are out of range.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden yet explains none of the three parameters. 'Active window boundaries' weakly implies what x and y are relative to, but the purpose of 'pid' and whether coordinates are window-relative or screen-relative are never stated.

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 and resource ('Dispatches a right-click'), which inherently differentiates it from the sibling 'click' and 'double_click'. It does not explicitly name an alternative or contrast, but the action 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 mention of when a plain click or hover is preferable, and no prerequisites such as the target window needing focus. The only guidance is the implicit constraint that the click occurs inside the active window.

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