veilbrowser

veil_click_at

Click at absolute viewport coordinates to interact with canvases, maps, or custom widgets when no snapshot reference exists.

Instructions

Trusted click at absolute viewport coordinates (x, y). Use when there is no snapshot ref to target — a canvas, map, or custom widget.

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": "veil_click_at"
  }
}

Input Schema

Name	Required	Description	Default
`x`	Yes
`y`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 29, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are present, so the description must bear full burden. The term 'trusted' is used without explanation of what trust entails (e.g., bypassing security checks). Basic behavior (clicking at coordinates) is implied but not elaborated on side effects or prerequisites.

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 sentences with no wasted words. The first sentence describes the action, the second gives use cases. Slightly more detail could be added without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple click tool with no output schema or nested objects, the description covers the core purpose, usage context, and parameter semantics partially. Missing details about 'trusted' and prerequisites, but sufficient for straightforward invocation.

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?

The input schema has 0% description coverage, so the description must add meaning. It clarifies that coordinates are 'viewport' coordinates, but doesn't specify units, range, or coordinate origin. This adds moderate value beyond the schema's bare type definitions.

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

Purpose5/5

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

The description clearly states 'Trusted click at absolute viewport coordinates (x, y)', specifying the verb 'click' and the resource 'absolute viewport coordinates'. It distinguishes from siblings like 'veil_click' by noting it targets when there is no snapshot ref, e.g., canvas or map.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: 'Use when there is no snapshot ref to target — a canvas, map, or custom widget.' This tells the agent when to choose this tool over others (e.g., veil_click for element references).

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