Execute playback, cutting, and timeline navigation shortcuts for DaVinci Resolve. Use play, pause, razor cut, zoom fit, fullscreen, blade, or select commands.
Executes playback, cutting, and timeline navigation shortcuts: 'play', 'pause', 'toggle', 'razor_cut', 'zoom_fit', 'fullscreen', 'blade', 'select'.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes |
| 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?
There are no annotations and the description only lists command names, failing to disclose potential side effects like timeline changes, playback state modifications, or dependence on a running application. This limits the agent's ability to predict the tool's impact, especially since it executes shortcut-like actions.
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, focused sentence that lists all relevant actions without any fluff. It is well-structured and immediately conveys the tool's scope, making it easy to scan and understand.
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?
Given the tool's simplicity (single parameter, no output schema), the description provides sufficient context for basic usage. It lacks details about return values or broader workflow integration, but that is not critical for a transport command. It is mostly complete.
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 schema provides only a required string 'action' with no enum or description (0% coverage). The description compensates by enumerating valid values ('play', 'pause', 'toggle', etc.), giving the agent concrete parameter options. However, it does not explain what each action does, so it is not fully comprehensive.
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 tool's purpose with a specific verb ('Executes') and identifies the resource ('playback, cutting, and timeline navigation shortcuts'), listing concrete actions. It is easily distinguishable from sibling tools that perform different tasks like status checks or page switches.
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?
The description provides no explicit guidance on when to use this tool versus alternatives. It simply lists available shortcuts without explaining conditions or contexts, leaving the agent to infer when transport actions are appropriate compared to other davinci_* tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.