Skip to main content
Glama
bigduu

Nova

by bigduu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

right_click

Perform a right-click at X/Y coordinates in the most recent capture's pixel space, optionally grounding it to an OCR center or visual coordinate.

Instructions

Grounded right click in the most recent capture's pixel space. Pass source=ocr_center for an OCR-returned center; otherwise the reported route defaults to visual_coordinate.

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
sourceNoGrounding source for route reporting. Use `ocr_center` only for a center returned by the immediately preceding OCR result. Omit/default `visual_coordinate` for a focused screenshot/zoom coordinate.
backgroundNoDeliver in the background to the captured window's process (native apps only; browsers/Electron ignore it). Default false = foreground.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • addedInput schema / $defs
      Added value: +{
+  "CoordinateActionSource": {
+    "oneOf": [
+      {
+        "const": "ocr_center",
+        "description": "Center returned by the immediately preceding focused OCR result.",
+        "type": "string"
+      },
+      {
+        "const": "visual_coordinate",
+        "description": "Coordinate read from the immediately preceding focused screenshot/zoom.",
+        "type": "string"
+      }
+    ]
+  }
+}
    • addedInput schema / properties / source
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/CoordinateActionSource"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Grounding source for route reporting. Use `ocr_center` only for a center\nreturned by the immediately preceding OCR result. Omit/default\n`visual_coordinate` for a focused screenshot/zoom coordinate."
+}
    • removedInput schema / title
      Removed value: -"ClickParams"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the click is 'grounded' in the most recent capture's pixel space, a non-obvious behavioral constraint, but it says nothing about side effects (context menu), whether it requires a foreground window, or how it interacts with existing state.

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?

Two tight sentences with the core action front-loaded and the source-routing caveat second. No filler, though the second clause is dense and could be marginally easier to parse.

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 4-param mutation tool with no annotations and no output schema, the definition covers grounding and source routing but omits return behavior, the background-delivery implications, and alternative-selection context. Adequate but with clear gaps.

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 50%: source and background are well documented in-schema, but x/y carry no schema description. The description partially compensates by establishing that coordinates live in 'the most recent capture's pixel space,' which is essential context for x/y, but gives no format, range, or origin details.

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+resource ('right click') and scopes it to 'the most recent capture's pixel space,' which clearly separates it from left_click, double_click, and ax_click. It does not explicitly name those siblings, but the action and grounding are unambiguous.

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 routing rule for source ('pass source=ocr_center for an OCR-returned center; otherwise defaults to visual_coordinate') is clear, but there is no guidance on when to choose right_click over ax_click, click_mark, or left_click, nor any prerequisite/exclusion context. Usage is implied rather than spelled out.

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

Deploy Server

Other Tools