Skip to main content
Glama

launch

Starts DaVinci Resolve when not running, then waits for its scripting API to respond so AI assistants can control it.

Instructions

Start DaVinci Resolve (if not running) and wait until the scripting API answers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two useful traits: it is conditional ('if not running') and it blocks until the API answers. However, it says nothing about what happens on timeout, whether failure raises an error or returns a status, whether it leaves a partially started process, or what the call returns.

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?

One sentence, front-loaded with the primary action, with the conditional and the blocking behavior attached in order of importance. No wasted wording.

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 one-parameter lifecycle tool this is close to adequate: the core action and its blocking nature are stated. But the only parameter is undocumented and failure/timeout semantics are absent, which matters for a tool whose whole job is to wait for a service to become available.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter 'wait' (default 90) is never mentioned in the description. The most likely interpretation is a timeout in seconds, but the agent must guess the unit and whether exceeding it aborts the launch or merely returns early.

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 gives a specific verb and resource: start DaVinci Resolve and block until the scripting API responds. That is a distinct action no sibling tool in the list performs, so an agent can identify it without ambiguity, though it never explicitly contrasts itself with siblings.

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

Usage Guidelines3/5

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

Usage context is implied by the parenthetical '(if not running)', which tells the agent this is safe to call as a prerequisite before other API calls. There is no explicit statement of when not to use it, no mention of calling it before other tools, and no alternatives for the already-running case.

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