DaVinci Director MCP

by kashyaprahul12659

Overview Schema Source Related Servers Discussions Admin

Python

Local

davinci_ai_cursor_move

Move the glowing AI cursor badge to specific coordinates in DaVinci Resolve for visual guidance during editing.

Instructions

Displays the virtual glowing AI cursor badge at 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_ai_cursor_move"
  }
}

Input Schema

Name	Required	Default
`x`	Yes
`y`	Yes
`label`	No	Antigravity Active

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

There are no annotations to clarify side effects, and the description only says 'Displays' without explaining whether the cursor is actually moved, whether the badge persists, or what happens to a previously displayed badge. The name 'cursor_move' implies movement, but the description only mentions displaying a badge, leaving ambiguity.

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, compact sentence with no unnecessary wording. It directly states the action, object, and location.

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

Completeness2/5

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

With no annotations and no usage context, the description leaves out important operational details such as side effects, success or failure conditions, and interaction with the UI. An output schema exists, so return values are not the main gap, but the lack of behavioral context is significant for a tool that interacts with a video editor interface.

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 explicitly maps x and y to coordinates, which adds meaning beyond the bare schema. However, the 'label' parameter is not mentioned in the description, and there are no parameter descriptions in the schema, so it is not fully covered.

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 ('Displays') and the object ('virtual glowing AI cursor badge') at a specific location ('coordinates (x, y)'). It distinguishes itself from sibling tools like ghost_click or transport by focusing on a visual cursor badge, though it does not explicitly address the 'move' in the tool name.

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?

No guidance is provided about when to use this tool versus alternatives such as ghost_click, seamless_click, or micro_adjust. There is no mention of use cases, preconditions, or situations where this badge display would be appropriate.

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