waveform-MCP

Overview Schema Source Related Servers Discussions Admin

desktop_click

Click at specified screen coordinates using a mouse button (left, right, or middle) to interact with the desktop interface. Use after taking a screenshot to target elements precisely.

Instructions

Click at screen coordinates. Use desktop_screenshot first to know what's where. button ∈ {left, right, middle}.

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

Input Schema

Name	Required	Default
`x`	Yes
`y`	Yes
`button`	No	left
`clicks`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A3.9/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 disclosure burden. It states the click action and button choices but doesn't disclose side effects, coordinate system origin, or behavior of the clicks parameter. The screenshot-first advice adds useful context, but the tool's potentially destructive nature on a live desktop is left implicit.

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 short sentences with no filler. The core action is front-loaded, followed by the key usage prerequisite and button options. Every sentence earns its place.

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-parameter tool with no output schema and no annotations, the description is minimally sufficient but leaves gaps: coordinate system details, multi-click semantics, and safety caveats are absent. The screenshot-first instruction helps an agent avoid blind clicking, but the description could be more complete.

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 description clarifies that x and y are screen coordinates and lists the allowed button values. However, the clicks parameter is never mentioned, and the button enum is already fully defined in the schema. With 0% schema description coverage, this is only partial compensation for the undocumented parameters.

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 ('Click') and resource ('screen coordinates'), clearly distinguishing this tool from siblings like desktop_move and desktop_key. The purpose is immediately understandable and unambiguous.

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

Usage Guidelines4/5

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

The description explicitly instructs to use desktop_screenshot first, providing an actionable precondition and workflow context. It doesn't name alternatives or exclusions, but for a low-level input primitive this is reasonable guidance.

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

Deploy Server