Retrieves DaVinci Resolve version, current page, open project, and active timeline so you can verify the app's state before running further operations.
Get Resolve version, current page, open project and active timeline.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the burden. It is clearly a read of host state with no parameters and no apparent side effects, but it never states that it is read-only or what happens if Resolve isn't running (error vs. partial result).
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?
One front-loaded sentence with no filler; the field list is the useful content. Slightly terse for a tool with no output schema, but nothing is wasted.
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?
With no output schema and no annotations, the description compensates by enumerating what is returned (version, page, project, timeline). The only meaningful omission is failure behavior when Resolve is unavailable.
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?
Zero parameters, so the baseline is 4. Nothing in the description is needed for argument formation, and the schema fully covers the (empty) argument object.
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?
Specific verb ('Get') plus an enumerated set of resources: app version, current page, open project, active timeline. That distinguishes it from narrower siblings like get_timelines and list_projects, though it doesn't name the alternatives.
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 when-to-use statement, no exclusion of siblings such as ping (health check) or get_current_time. Usage is implied by the returned field list – a general state snapshot – but the agent must infer it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.