Skip to main content
Glama
bigduu

Nova

by bigduu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

double_click

Clicks twice at x,y coordinates in the most recent capture’s pixel space, choosing OCR-center or visual-coordinate grounding for targeted UI actions.

Instructions

Grounded double 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

A3.5/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 the coordinate space ('most recent capture's pixel space') that grounds the click, but says nothing about side effects, required permissions, failure when no capture exists, or whether the target window is brought to the foreground by default.

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

Conciseness5/5

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

Two tight sentences with the action and coordinate frame front-loaded, and the parameter routing appended second. No filler.

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 mutating input tool with no annotations and no output schema, the description covers the coordinate-grounding model but omits prerequisites (an existing capture), side effects, and failure modes. 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 documented in the schema, while x and y are bare numbers. The description partially compensates by framing x/y as living in 'the most recent capture's pixel space' and clarifying the default route, but adds no format or range detail for the coordinates themselves.

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: a double click 'grounded in the most recent capture's pixel space', which is more informative than the bare name. It implicitly distinguishes itself from left_click/right_click by naming the double-click action, but never explicitly contrasts with those siblings.

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?

Gives conditional guidance for the source parameter ('pass source=ocr_center for an OCR-returned center; otherwise defaults to visual_coordinate'), which is closest to routing guidance. It does not say when to choose this tool over left_click/right_click or what preconditions (a prior capture) must hold.

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