DaVinci Director MCP

by kashyaprahul12659

Overview Schema Source Related Servers Discussions Admin

Python

Local

davinci_ghost_click

Send a background click to DaVinci Resolve at given (x, y) coordinates, triggering UI actions without foreground focus.

Instructions

Dispatches a background click message to DaVinci Resolve at window coordinates (x, y).

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

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The term 'background click message' hints at non-intrusive behavior but doesn't explain what 'background' means, whether it requires window focus, if it is asynchronous, or any side effects. This is a significant gap for a tool that interacts with UI.

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 a single, front-loaded sentence with no wasted words. It clearly states the action and parameters without extraneous details.

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 simple two-parameter tool, the description covers the basics, but it lacks differentiation from similar click tools (seamless_click, ai_cursor_move) and doesn't explain the 'background' aspect. While an output schema exists (not shown), the description doesn't mention expected outcomes or return values. It's minimally sufficient but not comprehensive.

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 0%, so the description must compensate. It does add meaning by specifying that x and y are 'window coordinates', which clarifies they are not screen or global coordinates. However, it doesn't specify units, origin, or any constraints beyond that. This provides minimal but useful context.

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?

The description clearly states the action: it dispatches a click message to DaVinci Resolve at specific coordinates. The verb 'dispatches' and resource 'DaVinci Resolve' are specific. It does not explicitly differentiate from sibling tools like davinci_seamless_click or davinci_ai_cursor_move, but the core purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as davinci_seamless_click or davinci_ai_cursor_move. The description only states what it does without any context on preferred scenarios, prerequisites, or exclusions.

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