Performs a localized click at (x, y) and restores the mouse to its original position, enabling AI-driven UI automation in DaVinci Resolve without moving the cursor.
Performs a localized click at (x, y) with glowing AI badge telemetry and restores mouse position.
| Name | Required | Description | Default |
|---|---|---|---|
| x | Yes | ||
| y | Yes | ||
| label | No | Antigravity Action |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses some behavioral side effects: it clicks, emits glowing AI badge telemetry, and restores the mouse position. However, with no annotations, it does not mention potential failures, permissions, or other side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that communicates the core behavior without unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is sufficient for basic invocation with x and y, but the label parameter is unexplained and the relationship to similar sibling tools is not addressed. The output schema is noted as present but not detailed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The x and y parameters are reasonably explained by the description as click coordinates. The label parameter is present but completely unexplained, leaving ambiguity about its purpose and allowed values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: performing a localized click at specific coordinates, with the additional behaviors of glowing AI badge telemetry and restoring the mouse position. It is specific enough to understand the tool's core purpose, though it does not explicitly distinguish it from ghost_click.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is given about when to use this tool versus sibling tools like davinci_ghost_click or davinci_ai_cursor_move. The behavior of restoring the mouse position suggests a use case, but it is not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.