Wraith MCP Server

by YogevKr

Overview Schema Source Related Servers Discussions Admin

Python

Local

click_at

Click a point in the page, in CSS pixels (the same units as the snapshot's @ (x,y) points and the screenshot).

Instructions

Click a point in the page, in CSS pixels (the same units as the snapshot's @ (x,y) points and the screenshot).

Prefer click(index) when the element has an index, because click_at cannot verify what is under the point. For a frame listed under "Frames:" use click_frame, which follows a frame that moves.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.16.1Oct 23, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that `click_at` cannot verify what is under the point, which is a key limitation, but it does not describe side effects, whether the click waits, or what `include_snapshot` changes.

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?

The description is front-loaded with the core purpose and coordinate semantics, then gives alternative-tool guidance. It is concise and every sentence adds useful information.

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?

An output schema exists, so return values need not be explained. The description covers the core operation, coordinate units, limitations, and sibling routing, but leaves `include_snapshot` unexplained despite the schema having no descriptions.

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 description coverage is 0%, so the description must explain all parameters. It clarifies that `x` and `y` are in CSS pixels and match snapshot `@ (x,y)` points and screenshots, but it says nothing about the `include_snapshot` parameter.

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 states a specific verb and resource: click a point in the page, in CSS pixels. It also distinguishes this from `click(index)` and `click_frame`, so an agent can tell exactly what this tool does and when it differs from siblings.

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?

The description explicitly directs the agent to prefer `click(index)` when the element has an index and to use `click_frame` for frames. This provides clear alternative-routing guidance rather than leaving the agent to infer tool selection.

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